Use the session profile to write when running aws configure #2972
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.
Previously the command
aws configure
would only use the profile present in the parsed globals to pass to theConfigFileWriter
, but sourced the profile from the session everywhere else. This would cause issues when the profile is set via an environment variable as the updated values would be written to the wrong section. This updates the configure command to consistently use the profile on the session and updates the unit test to rely on the session rather than the parsed globals.Fixes #2970