fix: NuGet job can't write to SSM when using secret role #1803
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.
When the NuGet publishing script assumes a role to retrieve the API key secret, it pollutes the global environment variables with the role credentials.
When we then later try to write to SSM, it uses the wrong role (the secret role instead of the CodeBuild role).
Retrieve the secret credentials in a subshell so they don't interfere with the CodeBuild credentials.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.