Hello - I have a question regarding stack reference dependencies. Here’s our use case: We have a project that creates a VPC and an EKS cluster along with some common resources. We have a second project that references the first projects outputs to create deployments, etc. That works great.
I can get into a weird state, however, if I try to delete the cluster stack without first deleting stacks that are dependant on it.
So, what I’d like to do is: When I deploy a child stack, I want to tell the parent stack that it now has a dependency. This could, hopefully, let me raise an error if I try to delete the parent stack without first deleting the child stacks.
Is anyone aware of a way a child stack can inject either configuration or state into a parent stack? Seems a bit odd, I realise, so if there’s a better way of handling this on a self-managed object storage backend, I’d love some ideas.