-
Notifications
You must be signed in to change notification settings - Fork 249
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
[request]: Please add support for overriding profile file paths #237
Comments
I think this would be a reasonable feature. Did you see this section: https://awslabs.github.io/aws-sdk-rust/aws_config/profile/fn.load.html#location-of-profile-files?
But for some environments, I imagine that those variables aren't practical to set |
Filed smithy-lang/smithy-rs#733 to track / prioritize fixing the docs. |
I did see that section, for my use case mutating global environment variables is not ideal. |
This feature was released in |
|
Community Note
Tell us about your request
Please add an option to ProfileFileCredentialsProvider to load credentials from a nonstandard path.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Certain credential deployment systems work by placing credentials in a well-known path. Currently it is not possible to parse these credentials using the AWS SDK for rust, because it is not possible to override the profile path.
The rustdoc suggests
aws_config::profile::load
could be used to override this, but the rustdoc for this method does not provide a clear path to doing so (indeed, the Fs and Env arguments are not even rustdoc'd). When all you need is to load credentials, that's a lot more complexity than you'd need.Are you currently working around this issue?
I am using rusoto to parse the profile and writing a custom ProvideCredentials to translate this to the Aws SDK credentials.
The text was updated successfully, but these errors were encountered: