Refactoring Config loading, replacing the need for a Session. #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds an
external
package to load external configuration data to the SDK. This replaces the loading work performed by thesession
package. In addition this will remove the need for asession
and the SDK can remove this concept.The new
external
config loading package is based on modular components that are plugged together to load external configuration, and resolve that configuration into anaws.Config
value. This allows customers the flexibility to configure the SDK as they need.This does not support service specific external configuration. It is not defined how or if this will be supported in the future.
Load default configuration without any customization or options:
Load default configuration while also providing a shared config profile
in addition to the default shared config and env config.
TODO:
external
package.aws.Config
).WithSharedConfigProfile("test-profile"), WithEndpointResolver(StaticEndpoint("abc")), WithRegion("blah"),
or is this complicating the loader with AWSConfig specific values.?