You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have our own library of playbook L3 constructs when deploying with CDK. One of them a composite arrangement of ASG, ALB, with options for CloudFront, WAF, public HTTP API Gateway, etc. This construct type is meant to be deployed as part of an application layer stack, which has dependency on a base stack that covers the fundamental infrastructure resources like VPC, security groups, S3 buckets, etc.
When running cdk diff and deploy of the base stack of a brand new system environment, I noticed the VPC link of the API Gateway AWS::ApiGatewayV2::VpcLink of the above-mentioned construct has somehow found its way into the template of the base stack instead of the yet-to-be-deployed application stack.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
https://repost.aws/questions/QUVCECvtYoRCK71OAZ0bxS9w/cdk-forward-deploying-resource-from-another-stack
We have our own library of playbook L3 constructs when deploying with CDK. One of them a composite arrangement of ASG, ALB, with options for CloudFront, WAF, public HTTP API Gateway, etc. This construct type is meant to be deployed as part of an application layer stack, which has dependency on a base stack that covers the fundamental infrastructure resources like VPC, security groups, S3 buckets, etc.
When running cdk diff and deploy of the base stack of a brand new system environment, I noticed the VPC link of the API Gateway AWS::ApiGatewayV2::VpcLink of the above-mentioned construct has somehow found its way into the template of the base stack instead of the yet-to-be-deployed application stack.
What can cause CDK to shift a resource from a dependent stack into a dependency stack? This is not desired behaviour.
Beta Was this translation helpful? Give feedback.
All reactions