-
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
(aws-cdk): After CDK v2 upgrade, my Gitlab CI/CD started failing #17832
Comments
Gitlab CI/CD is using the alpine container with aws-cdk, aws-cli, python and few other things...
|
Upon further tinkering and adding cdk 2.x $ cdk diff
...
[-] ]
[-] }
[-] ]
[-] }
[-] ]
[-] ]
[-] }
[+] "45b7ed524ce2b119dd4f2b8642ae8bfaf0df45bc6bd705072ae4ee6d1a999241.zip"
Other Changes
[+] Unknown Rules: {"CheckBootstrapVersion":{"Assertions":[{"Assert":{"Fn::Not":[{"Fn::Contains":[["1","2","3","4","5"],{"Ref":"BootstrapVersion"}]}]},"AssertDescription":"CDK bootstrap stack version 6 required. Please run 'cdk bootstrap' with a recent version of the CDK CLI."}]}}
Cleaning up project directory and file based variables
00:01
+ set -eo pipefail
+ set +o noclobber
+ eval '$'\''rm'\'' "-f" "/builds/acme/cf/cloudfront-factory.tmp/CI_SERVER_TLS_CA_FILE"
'
+ :
++ rm -f /builds/acme/cf/cloudfront-factory.tmp/CI_SERVER_TLS_CA_FILE
+ exit 0
ERROR: Job failed: exit code 1 cdk 1.x $ cdk diff
Stack acmeStaticCFStack
Resources
[~] AWS::CloudFront::Distribution distro distro40218A07
└─ [~] DistributionConfig
├─ [~] .Aliases:
│ └─ @@ -1,4 +1,4 @@
│ [ ] [
│ [-] "acme.com",
│ [+] "baz.com"
│ [ ] ]
└─ [~] .Comment:
├─ [-] Static distro for acme.
└─ [+] Static distro for baz.
+ exit 0
Saving cache for successful job
+ set -eo pipefail
+ set +o noclobber
+ :
+ eval '$'\''rm'\'' "-f" "/builds/acme/cf/cloudfront-factory.tmp/CI_SERVER_TLS_CA_FILE"
'
++ rm -f /builds/acme/cf/cloudfront-factory.tmp/CI_SERVER_TLS_CA_FILE
+ exit 0
Job succeeded It seems that in v2 PR addressing this issue (#4650) either got reverted or the bug got reintroduced. @jogold Would you mind taking a peek and providing your take on this issue? |
After adding [-] ]
[-] ]
[-] }
[+] "45b7ed524ce2b119dd4f2b8642ae8bfaf0df45bc6bd705072ae4ee6d1a999241.zip"
Other Changes
[+] Unknown Rules: {"CheckBootstrapVersion":{"Assertions":[{"Assert":{"Fn::Not":[{"Fn::Contains":[["1","2","3","4","5"],{"Ref":"BootstrapVersion"}]}]},"AssertDescription":"CDK bootstrap stack version 6 required. Please run 'cdk bootstrap' with a recent version of the CDK CLI."}]}}
+ true
+ exit 0
Saving cache for successful job
00:11
+ set -eo pipefail
+ set +o noclobber
+ :
+ eval '$'\''rm'\'' "-f" "/builds/acme/cf/cloudfront-factory.tmp/CI_SERVER_TLS_CA_FILE"
'
++ rm -f /builds/acme/cf/cloudfront-factory.tmp/CI_SERVER_TLS_CA_FILE
+ exit 0
Job succeeded |
You're correct. The way our CLI handled expired feature flags (like Fix is #17862 |
Thank for confirming this @njlynch. And thanks for providing the PR for it. Much appreciated. 👍 😊 |
Fix will go out with next v2 release. |
|
General Issue
After CDK v2 upgrade, my Gitlab CI/CD started failing
The Question
Hello,
I tarted migrating my CDK v1 repos/apps to CDK v2, and my Gitlab CI/CD pipeline started failing after
cdk diff
command. I'm not getting any errors when I run ci/cd jobs (on the same runner) with CDK v1. Any input is appreciated.I did run
cdk boostrap
beforehand which created new S3 buckets.CDK CLI Version
2.0.0 (build 4b6ce31)
Framework Version
No response
Node.js Version
v16.13.1
OS
OSx 11.6.1 Big Sur
Language
Typescript
Language Version
3.9.7
Other information
No response
The text was updated successfully, but these errors were encountered: