AST-171789 Fix AWS secret export prefix mismatch in release workflow - #500
Merged
Merged
Conversation
The GPG signing step in the Maven release job resolves its key and credentials to empty because the AWS secrets-manager fetch step exports each secret key prefixed with a sanitized version of the secret name, while downstream steps read the plain, unprefixed env var names. Adding a leading blank alias to the secret-ids list makes the action export the keys unprefixed, matching what the rest of the workflow already expects. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
cx-alon-rosenhek
approved these changes
Sep 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The Maven release job's GPG signing step was failing because the signing key and related credentials resolved to empty at the point they're used.
The AWS secrets-manager fetch step exports each key prefixed with a sanitized version of the secret's name, but the workflow's later steps read the plain, unprefixed names. Adding a blank alias to the fetch step's secret list makes it export the keys unprefixed, matching what the rest of the workflow already expects.