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

Support for Cloud Provider Default Authentication Chains #2637

Open
z0r0 opened this issue Jul 12, 2024 · 0 comments
Open

Support for Cloud Provider Default Authentication Chains #2637

z0r0 opened this issue Jul 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@z0r0
Copy link

z0r0 commented Jul 12, 2024

Describe the problem you are trying to solve
Different cloud providers have different priorities to how they resolve authentication metadata (mostly retrieving tokens). Having tremor honor those priorities helps users avoid risks around passing service account credentials in configuration files, or passing them as environment variables.

Describe the solution you'd like
For cloud provider specific connectors, it would be nice if tremor implemented the cloud provider best practices for implementing authentication. A first step might be implementing the default provider chain for S3. Google has a similar mechanisim, but unfortunately no rust support for it (yet)

Notes

If this is an implementation of an RFC provide a URL
to the RFC this enhancement implements.

If this is a major enhancement or contribution an RFC may be required. It is ok to submit an enhancement
first and our core team will assist with major contributions. In general, major contributions should be
discussed with the community before submission.

@z0r0 z0r0 added the enhancement New feature or request label Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant