fix(cli): hotswap doesn't update SSM parameter environment variables properly#26382
fix(cli): hotswap doesn't update SSM parameter environment variables properly#26382mergify[bot] merged 6 commits intoaws:mainfrom
Conversation
aws-cdk-automation
left a comment
There was a problem hiding this comment.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.
|
Exemption Request: This change should be covered with cli integ tests. |
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
…properly (aws#26382) Closes aws#25387 Closes aws#25483 The actual value for a CfnParameter backed by a SSM parameter is returned via `ResolvedValue` (and only for SSM parameters, [doc](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_Parameter.html#API_Parameter_Contents)). We use the field from DescirbeStacks API response to populate `stackParams`, instead of `ParameterValue`, which is just a parameter's name. As far as I checked it is not a breaking change. The `parameter` field is not a public API, and internally the values of SSM parameters are only used for hotswap. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Closes #25387
Closes #25483
The actual value for a CfnParameter backed by a SSM parameter is returned via
ResolvedValue(and only for SSM parameters, doc). We use the field from DescirbeStacks API response to populatestackParams, instead ofParameterValue, which is just a parameter's name.As far as I checked it is not a breaking change. The
parameterfield is not a public API, and internally the values of SSM parameters are only used for hotswap.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license