cli: add persistent stacks to integ test #5682
Labels
@aws-cdk/aws-ec2
Related to Amazon Elastic Compute Cloud
closed-for-staleness
This issue was automatically closed because it hadn't received any attention in a while.
effort/large
Large work item – several weeks of effort
feature-request
A feature should be added or improved.
management/devenv
Related to CDK development/build environment
ops-excellence
Operational Excellence
p2
package/tools
Related to AWS CDK Tools or CLI
To discover issues like #5469, add a stack to the integration tests that is NOT cleaned up after every deployment.
Instead, we'll be exercising the CDK's ability to keep updating an existing stack with critical resources in there (to start, a Vpc but others may be added).
For most updates this should be a no-op so it shouldn't add more than 10s to a typical test run.
The text was updated successfully, but these errors were encountered: