Describe the bug
cdk deploy --hotswap should notice if any non-Lambda changes need to be deployed, but it fails to see when there has been a CfnOutput change, e.g. a different output name.
Expected Behavior
cdk deploy --hotswap would see that a CfnOutput changed and deploy the changes instead of hotswapping.
Current Behavior
If a CfnOutput's name changes, cdk deploy --hotswap thinks it only needs to hostswap, so the CfnOutput's name does not change.
Reproduction Steps
cdk deploy a stack that includes a CfnOutput- make an edit to the
CfnOutput's name
- run
cdk deploy --hotswap
- Expected behavior:
CfnOutput's name should change
Actual behavior: ✨ hotswapping resources: is printed and the CfnOutput's name does not change
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.20.0
Framework Version
No response
Node.js Version
v14.16.0
OS
Windows 10
Language
Python
Language Version
No response
Other information
No response
Describe the bug
cdk deploy --hotswapshould notice if any non-Lambda changes need to be deployed, but it fails to see when there has been aCfnOutputchange, e.g. a different output name.Expected Behavior
cdk deploy --hotswapwould see that aCfnOutputchanged and deploy the changes instead of hotswapping.Current Behavior
If a
CfnOutput's name changes,cdk deploy --hotswapthinks it only needs to hostswap, so theCfnOutput's name does not change.Reproduction Steps
cdk deploya stack that includes aCfnOutputCfnOutput's namecdk deploy --hotswapCfnOutput's name should changeActual behavior:
✨ hotswapping resources:is printed and theCfnOutput's name does not changePossible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.20.0
Framework Version
No response
Node.js Version
v14.16.0
OS
Windows 10
Language
Python
Language Version
No response
Other information
No response