How to avoid circular dependencies in AWS CloudFormation stacks using nested stacks?
I need help solving I'm having a hard time understanding I've tried everything I can think of but I've searched everywhere and can't find a clear answer... I'm trying to modularize my CloudFormation templates using nested stacks, but I'm running into circular dependency issues when referencing outputs from one stack to another. For example, I have two stacks defined: `NetworkStack` and `ApplicationStack`. The `NetworkStack` creates a VPC and outputs its ID, which the `ApplicationStack` needs to reference. However, the `ApplicationStack` also needs to create subnets, which depend on the VPC being fully created first. Here's a simplified version of what my `NetworkStack` looks like: ```yaml Resources: VPC: Type: AWS::EC2::VPC Properties: CidrBlock: 10.0.0.0/16 Output: VPCID: Value: !Ref VPC ``` And for the `ApplicationStack`: ```yaml Resources: Subnet: Type: AWS::EC2::Subnet Properties: VpcId: !ImportValue NetworkStack:VPCID CidrBlock: 10.0.1.0/24 ``` When I attempt to deploy, I get the following behavior: ``` Circular dependency between resources: 'NetworkStack' and 'ApplicationStack' ``` I know that CloudFormation does not support circular dependencies, so I tried to break this cycle by leveraging `AWS::CloudFormation::Stack` to create a nested stack for the `ApplicationStack` within the `NetworkStack`. However, this leads to additional complications and still doesn't resolve the circular reference. How can I structure my CloudFormation templates to avoid these circular dependencies while allowing both stacks to reference each other properly? Any best practices or design patterns that could help in this situation would be greatly appreciated. I'm using AWS CloudFormation with version 1.71.0 of the AWS CLI. I'm using Yaml 3.9 in this project. Could this be a known issue? This issue appeared after updating to Yaml 3.9. Thanks for any help you can provide! For context: I'm using Yaml on Ubuntu 22.04. I'm using Yaml 3.11 in this project.