We should add “short circuit” feature to the CLI which will skip change set creation and execution if the currently deployed template is identical to the one we are we’re requested to deploy.

Use Case

This will improve the user experience and will address two issues :

1. [aws-eks] Nested stacks always cause an update #6046: where nested stacks cause an update even if they haven’t changed. CloudFormation currently attempts to update nested stacks even if their template haven’t changed. This is because theoretically CFN can’t tell if the template had changed or not, but CDK nested stack templates are immutable and therefore if the URL didn’t change, we know for sure that an update is not needed.

2. "FAILED, No updates are to be performed" when adding a "Transform" to a stack #2553: creating a change set with no updates fails.

Proposed Solution

We should make this the default behavior but allow people to disable through something like --force

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

This is a 🚀 Feature Request