We have shared resources like the container registry, this sits in a shared resource group and is also tied to a subscription that might be different from the rest of the resources in the application environment setup.
With the existing implementation it is linked to the stack that first creates it. If this stack is torn down it will tear down the shared resources as well. This is obviously not desirable. We want a separate stack for this linked to the creation of an application and not the environment.
You can see the SetupResourceGroup and how it has a check on the stack if the resource group belongs to the current stack. That in itself should have been the warning signal.
We have shared resources like the container registry, this sits in a shared resource group and is also tied to a subscription that might be different from the rest of the resources in the application environment setup.
With the existing implementation it is linked to the stack that first creates it. If this stack is torn down it will tear down the shared resources as well. This is obviously not desirable. We want a separate stack for this linked to the creation of an application and not the environment.
You can see the
SetupResourceGroupand how it has a check on the stack if the resource group belongs to the current stack. That in itself should have been the warning signal.