Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URLs with S3 scheme in Copy URL menu #8753

Closed
cyberduck opened this issue Apr 17, 2015 · 9 comments
Closed

URLs with S3 scheme in Copy URL menu #8753

cyberduck opened this issue Apr 17, 2015 · 9 comments
Assignees
Labels
enhancement fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

8c3435f created the issue

S3 can be accessed with URIs where the scheme is 'S3' using tools like the AWS CLI (e.g., http://docs.aws.amazon.com/cli/latest/userguide/using-s3-commands.html) or EMR (e.g., http://docs.aws.amazon.com/ElasticMapReduce/latest/DeveloperGuide/emr-build-binaries.html)

Here's an example URL for a public file which links to a shell script:
s3://elasticmapreduce/bootstrap-actions/configure-hadoop

The attached patch allows users to browse files in Cyberduck, copy URLs in the new format and then paste them into code or as command-line arguments.


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We do support URLs s3://<container>/<key> in Cyberduck CLI.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [8753 steamer25]:

The attached patch allows users to browse files in Cyberduck, copy URLs in the new format and then paste them into code or as command-line arguments.

The patch seems to be missing.

@cyberduck
Copy link
Collaborator Author

8c3435f commented

Replying to [comment:2 dkocher]:

We do support URLs s3://<container>/<key> in Cyberduck CLI.

Another excellent use case for copying them out of the GUI :) .

@cyberduck
Copy link
Collaborator Author

8c3435f commented

Replying to [comment:3 dkocher]:

Replying to [8753 steamer25]:

The attached patch allows users to browse files in Cyberduck, copy URLs in the new format and then paste them into code or as command-line arguments.

The patch seems to be missing.

Sorry--I submitted the first page of the new issue form and then took a moment to generate the patch and double-check the formatting. Apparently, Trac made the issue active before I was able to attach the patch on the second page. The patch is attached now. Thanks for being super-responsive external image

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 5b56b17. Revised the patch to handle whitespace in key names.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We should extend support to allow s3:// schemes in the quick connect field.

@cyberduck
Copy link
Collaborator Author

8c3435f commented

Doh! On line 23 of the patch (the part that specifies the scheme of the URL being generated), I used a capital 'S' in S3. It should be lower case.

I.e.,

--- URI.create("S3:/" + file.getAbsolute()),
+++ URI.create("s3:/" + file.getAbsolute()),

@cyberduck
Copy link
Collaborator Author

8c3435f commented

Replying to [comment:8 steamer25]:

Doh! On line 23 of the patch (the part that specifies the scheme of the URL being generated), I used a capital 'S' in S3. It should be lower case.

I.e.,

--- URI.create("S3:/" + file.getAbsolute()),
+++ URI.create("s3:/" + file.getAbsolute()),

Took at look at 5b56b17 and it looks like you took care of it--thanks!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

As of 7f3046e you can now use URLs with s3:// or rackspace:// schemes in the user interface such as Quick Connect.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants