Open alanb-sony opened 1 year ago
This is tricky - what if we only synth one of the stacks?
I don't know how this is implemented internally, I'm not expecting CDK to do something to fix the error or detect it before deployment but it'd be nice if it caught the error from cloud formation
Oh, I see. I did not read the issue closely and misunderstood what you meant. Sure, getting the error from CloudFormation would be useful. I don't think calling this failure "silent" is fair, though - you get an error message.
Agree. It would be great if CDK can throw this error before CFN deployment.
Describe the bug
If two CDK stacks have
CfnOutput
with the sameexportName
then CDK fails with:Looking in the cloudformation events you can see the error "Export with name xxx is already exported by stack yyy" it'd be nice if CDK itself reported this error.
Expected Behavior
An error on the CDK console saying "Export with name xxx is already exported by stack yyy"
Current Behavior
The stack failed to deploy with no error message
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.60.0
Framework Version
No response
Node.js Version
16
OS
Linux
Language
Typescript
Language Version
No response
Other information
No response