fix(ci): add missing dollar signs in SSM parameter path variables #7695
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.



Issue number: closes #7689
Summary
Changes
Fixed a typo in
.github/workflows/update_ssm.ymlwhere 10 out of 12 SSM parameter path variables were missing the$prefix onPACKAGE_VERSION.When adding Python 3.14 support in commit a58cef7, the workflow was refactored to use shell environment variables instead of GitHub Actions expressions. However, during this refactor, the
$symbol was accidentally omitted on most lines, causing the literal string "PACKAGE_VERSION" to be used in parameter paths instead of the actual semantic version (e.g., "3.23.0").Lines fixed:
User experience
Before:
Users looking for version-specific SSM parameters for Python 3.11-3.14 (ARM64) and all x86_64 versions cannot find them for release 3.23.0.
For example, querying
aws ssm get-parameter --name "/aws/service/powertools/python/x86_64/python3.13/3.23.0" --region us-east-1returnsParameterNotFoundInstead, incorrectly named parameters exist at
/aws/service/powertools/python/x86_64/python3.13/PACKAGE_VERSIONAfter:
Future releases will create correctly named SSM parameters that users can reference in their CloudFormation templates and infrastructure code.
Note:
This fix prevents the issue in future releases. The v3.23.0 parameters will need to be recreated separately by re-running the update_ssm workflow for that version.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.