This message was deleted.

You could encapsulate your entire stack into a

ComponentResource

and then instead declare 1 of those for each region at the top of your stack. This would allow you to have a single

Production

stack. Or just do separate stack configs

I’m thinking separate stack configs is the way to go

This is a tricky question because it's highly dependent on an environment and your requirements for the "agility" of your resources. If your solution is using just 2 regions and will do for a long time. Then Stack per region is good. You can also make use of namespaces in config and have 1 stack for both regions like Joshua suggested.

Pulumi.production.yaml

us-region:config_key:  value

eu-region:config_key: value

then in code:

us_config = pulumi.Config('us-region')
eu-config = pulumi.Config('eu-region')

Yea I personally wouldn’t want multiple stacks per region. I’m just imagining stacks going out of sync because now you need to deploy multiple times per environment per release