AssumeRoleProvider Configuration Updates #906
rcoh
announced in
Change Log
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The API for
AssumeRoleProviderhas been updated to derive configuration fromSdkConfiginstead ofProviderConfig.An example of updating code to use the new API is here.
This provides a number of advantages, most importantly, making it possible to use
aws_config::load_from_envas the base set of configuration when constructing yourAssumeRoleProvider.If no custom configuration is provided,
build()will fall back to usingaws_config::from_env()as the source of configuration. This can be overidden withAssumeRoleProvider::builder("role...").configure(<sdkconfig>)In either case, this means that
regionis not required to be set unless you need a different value than you would otherwise get from the runtime environment.Finally:
AssumeRoleProvider::buildhas been renamedbuild_from_provider.build()will now source a credentials provider fromSdkConfiginstead. You can specifySdkConfigto source defaults from with.configure(&config)asyncBeta Was this translation helpful? Give feedback.
All reactions