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

Docker entrypoint: authentication for Azure Blob #420

Merged
merged 1 commit into from
Jun 21, 2022

Conversation

christophkreutzer
Copy link
Contributor

When using s3proxy as a proxy for S3 -> Azure Blob Storage, one needs to set the authentication parameters. When running in a container, these can be exposed via environment variables, but are currently not passed through to the jclouds config.

This is how we got it running for us in a custom build of the container.
Should I also add the options for other backends? Or do you see options for a generic solution?

Maybe also corresponds to #404

When using the s3proxy as a proxy for S3 -> Azure Blob Storage, one needs to set the authentication parameters. When running in a container, these can be exposed via environment variables, but are currently not passed through to the jclouds config.
@gaul gaul merged commit 1d450fa into gaul:master Jun 21, 2022
@gaul
Copy link
Owner

gaul commented Jun 21, 2022

Thank you for your contribution @christophkreutzer! I am happy to add configs as one-offs but if there is some better mechanism please suggest it.

@christophkreutzer christophkreutzer deleted the patch-1 branch June 21, 2022 07:04
@christophkreutzer
Copy link
Contributor Author

Hello @gaul, thanks for merging. I have no clear idea about a generic implementation, at least with env variables.

Another way would be allow passing a properties file (which could be Docker file mount or a configmap mount on Kubernetes), but that's a bit less elegant to use in my opinion.

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

Successfully merging this pull request may close these issues.

2 participants