(Translated by https://www.hiragana.jp/)
Figure out what to do about locations · Issue #703 · gaul/s3proxy · GitHub
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

Figure out what to do about locations #703

Open
gaul opened this issue Oct 8, 2024 · 0 comments
Open

Figure out what to do about locations #703

gaul opened this issue Oct 8, 2024 · 0 comments

Comments

@gaul
Copy link
Owner

gaul commented Oct 8, 2024

jclouds abstracts the physical placement of data in Location which can be configured via the jclouds.region and jclouds.regions properties. This is poorly documented in the S3Proxy and it isn't obvious how to create a new bucket when using the Azure backend. Ideally this should work out of box and us-east1 should map to whatever the provider's default location is. Other user-specified locations should map to the underlying storage backend location.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant