Skip to content
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

fix: NuGet job can't write to SSM when using secret role #1803

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented Dec 12, 2024

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.

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.
@rix0rrr rix0rrr requested a review from a team December 12, 2024 11:08
@cdklabs-automation cdklabs-automation added this pull request to the merge queue Dec 12, 2024
Merged via the queue into main with commit 424ce20 Dec 12, 2024
6 checks passed
@cdklabs-automation cdklabs-automation deleted the huijbers/no-interference-pact branch December 12, 2024 11:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants