[CDKv2GA]: Create "canaries" for CDKv2 #16593
Assignees
Labels
aws-cdk-lib
Related to the aws-cdk-lib package
effort/medium
Medium work item – several days of effort
in-progress
This issue is being actively worked on.
ops-excellence
Operational Excellence
p1
Milestone
Comments
njlynch
added
ops-excellence
|
Paused this while I was on-call last week. Resuming today, should have a PR out in a day or so! |
mergify bot
pushed a commit
that referenced
this issue
Nov 3, 2021
…-cdk version (#17285) If an environment variable, `$RELEASE_TAG` is defined, it will be appended to the end of the `npm install aws-cdk@` command. This will allow us to run canaries that test against v2 by specifying `RELEASE_TAG=next` in the environment variables. If `$RELEASE_TAG` is not defined, `npm install aws-cdk@latest` will be used. This PR also includes a comment in `release-notes.ts` that the v2 publishing verification canary is dependent on the format of the release notes. part of #16593, see https://github.com/cdklabs/cdk-ops/pull/1769 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
|
TikiTDO
pushed a commit
to TikiTDO/aws-cdk
that referenced
this issue
Feb 21, 2022
…-cdk version (aws#17285) If an environment variable, `$RELEASE_TAG` is defined, it will be appended to the end of the `npm install aws-cdk@` command. This will allow us to run canaries that test against v2 by specifying `RELEASE_TAG=next` in the environment variables. If `$RELEASE_TAG` is not defined, `npm install aws-cdk@latest` will be used. This PR also includes a comment in `release-notes.ts` that the v2 publishing verification canary is dependent on the format of the release notes. part of aws#16593, see https://github.com/cdklabs/cdk-ops/pull/1769 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Exactly like the CDKv1 infrastructure, CDKv2 needs to have a regularly scheduled job that downloads and installs the CDK, and uses it to deploy (and delete) a stack. The canary should be monitored and alarmed exactly as the existing v1 canary is today.
The text was updated successfully, but these errors were encountered: