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

setting SECRETS SCOPE by ENDPOINT? #5

Open
cboettig opened this issue Nov 28, 2024 · 0 comments
Open

setting SECRETS SCOPE by ENDPOINT? #5

cboettig opened this issue Nov 28, 2024 · 0 comments

Comments

@cboettig
Copy link

duckdb documentation describes how to create multiple secrets for the same service, e.g. if we have two S3 buckets that need different credentials. The directions indicating scoping based on bucket name.

However, I commonly encounter the case where I need to access two different S3 services at different endpoints -- for instance, S3 buckets data.source.coop , S3 buckets on a local minio instance, S3 buckets on AWS. It would be natural to scope these by the endpoint name, not the bucket name -- I may have the same credentials for multiple buckets, and I may have the same bucket name on different endpoints.

I think it is something of a bug that scope focuses on bucket name but ignores endpoint. Would you consider adding support for this?

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