-
Notifications
You must be signed in to change notification settings - Fork 4k
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(core): DefaultSynthesizer
deployments are never skipped
#17099
Conversation
The `DefaultSynthesizer` always adds an SSM parameter with the bootstrap stack version, so that it can check that the bootstrap stack has a recent enough version. Unfortunately, the CDK CLI will refuse to short-circuit any deployment that uses SSM parameters, because it can't tell if the parameter has changed, and so it has to pessimize. Adding a magic marker to the description of the parameter will now exempt it from the check. Fixes #16959.
@@ -600,7 +600,7 @@ function addBootstrapVersionRule(stack: Stack, requiredVersion: number, bootstra | |||
|
|||
const param = new CfnParameter(stack, 'BootstrapVersion', { | |||
type: 'AWS::SSM::Parameter::Value<String>', | |||
description: 'Version of the CDK Bootstrap resources in this environment, automatically retrieved from SSM Parameter Store.', | |||
description: `Version of the CDK Bootstrap resources in this environment, automatically retrieved from SSM Parameter Store. ${cxapi.SSMPARAM_NO_INVALIDATE}`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the pipelines integ tests (e.g., https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/pipelines/test/integ.newpipeline.expected.json#L2306) are going to need an update.
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 master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
) The `DefaultSynthesizer` always adds an SSM parameter with the bootstrap stack version, so that it can check that the bootstrap stack has a recent enough version. Unfortunately, the CDK CLI will refuse to short-circuit any deployment that uses SSM parameters, because it can't tell if the parameter has changed, and so it has to pessimize. Adding a magic marker to the description of the parameter will now exempt it from the check. Fixes aws#16959. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The
DefaultSynthesizer
always adds an SSM parameter with the bootstrapstack version, so that it can check that the bootstrap stack has
a recent enough version.
Unfortunately, the CDK CLI will refuse to short-circuit any deployment
that uses SSM parameters, because it can't tell if the parameter has
changed, and so it has to pessimize.
Adding a magic marker to the description of the parameter will now
exempt it from the check.
Fixes #16959.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license