-
Notifications
You must be signed in to change notification settings - Fork 55
fix(rt): plumb client configuration properties #730
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix and ship.
The codegen diff preview action appears to have a bug in it related to getting the correct version of smithy-kotlin to use. Ignore for now, I'll create an issue for it. (You can also probably change the smithy-kotlin version in gradle.properties to match and it should work again).
| private val profileName: String? = null, | ||
| private val platformProvider: PlatformProvider = Platform, | ||
| httpClientEngine: HttpClientEngine? = null, | ||
| region: String? = null, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix: Needs documentation
| AWS region to make requests to | ||
| """.trimIndent() | ||
| propertyType = ClientConfigPropertyType.Required() | ||
| order = -1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as smithy-kotlin, leave yourself some room between the default to allow for insertion of properties in-between these if necessary.
|
Kudos, SonarCloud Quality Gate passed!
|








Plumb client configuration properties through to other client configuration properties
Issue #
#711
Description of changes
When a user specifies an HTTP engine or region in the client configuration, these are not passed through to the CredentialsProvider. This PR passes those configurations to the DefaultCredentialsChainProvider, and also passes
regionfrom the DefaultCredentialsChainProvider to the ProfileCredentialsProvider.Note: if a user specifies a custom CredentialsProvider, they will still need to specify the engine both there and in the general client configuration.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.