Right, I just came across this part of the doc:
https://terraspace.cloud/docs/dependencies/exclude-stacks/
which will allow me to restrict the stack by first applying a TS_ENV=global
however it will come with the following draw backs which makes this approach not suitable:
-
I will be unable to reference the output from the global env to the regional env, example: getting the
network_name
from the global env in the regional one, to create related subnets. Ref How to use outputs between Multi Region stacks -
It will force me to create multiple stacks example:
network_global
-network
etc… where I would have preferred this distinction within the stack it self
Is there a clean way to achieve this and be able to terraspace run-all up
with global and non global resources?