Child stacks not deploying after upgrading to CDK 2.0

[andsgAWS]

Back in early December we upgraded to CDK 2.0 and after some time, we've come to find that the child stacks aren't being updated anymore (this package is updated infrequently and most of the changes since December have been minor). We believe the issue is that the feature flag stackRelativeExports is turned on by default in CDK 2.0, and our deployment group only specifies the parent stack, i.e. stacks: [parentStack] instead of something like stacks: [...parentStack.stacks]. When updating the underlying CDK code and deploying, the deployment failed, indicating that the stacks must destroy each other to in order to recreate using the latest code. Since we have a circular dependency between our S3 and KMS stacks, this action failed. Our currently though is that we can set the feature flag to false, essentially reverting to some CDK 1.0 behavior, and then update the deployment group stack to something like [...parentStack.stacks], or to change the stack we extend our child stacks from, from DeploymentStack to cdk.NestedStack, and then subsequently remove the feature flag once the child stacks are updated, resolving our issue and landing us on CDK 2.0.

Are there any suggestions or actions that we can take while working through this? Any guidance would be greatly appreciated. Additionally, it surfaced recently that we may have forgotten to bootstrap CDK 2.0 resources prior to the first CDK 2.0 deployment (which somehow still succeeded). There are more questions than answers here and it's not necessarily a problem right now, however it could become a large problem in the near future if we don't resolve this.

Thanks in advance! Let me know if any other information is needed.

[kellertk]

Hi there @andsgAWS. You're talking about DeploymentStacks and the like. These are internal-only AWS CDK constructs that are not part of the public release of CDK. Instead of discussing this on GitHub, where it will be of little use to the community at large, let's take this to an internal ticket. Please submit one at CTI AWS/CDK/Internal Customer Issue. You might also check with other internal-only resources, like the NADE team, who are the owners of the internal-only CDK constructs.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.