This message was deleted.
# azures
sparse-intern-71089
06/01/2023, 6:54 AMThis message was deleted.
d
damp-honey-93158
06/02/2023, 10:11 PMmay I ask why your production config has anything to do with a dev environment at all? perhaps you might think about splitting the shared resources into a stack that both dev and production then reference.
damp-honey-93158
06/02/2023, 10:13 PMgiven that pulumi stacks are responsible for their underlying resources, this would be a good fit for you. (we do this in our apps too). then in the “shared” stack, you can have some kind of ‘state flag’ that indicates what you want pulumi to do to any of these resources .
c
cuddly-napkin-89521
06/03/2023, 6:52 AMHello @damp-honey-93158, thank you for reply. Our DNS zone is configured in Dev subscription, as it is not possble to have same dns zones in different subscriptions, at least I think is not possible, and by my company rules, zone is configured manually, just added in Azure portal, and we are creating subdomains via Pulumi
d
damp-honey-93158
06/03/2023, 9:35 AMYou can cross subscriptions - but I don’t believe you can go across tenants. And yep - they are going to need to be unique. You can use pulumi to reference resources across tenants, but in this case you will need to instantiate your own Azure provider, that uses appropriate AZURE/ARM_CLIENT_ID, AZURE/ARM_TENANT_ID, AZURE/ARM_SUBSCRIPTION_ID (and so on)
c
cuddly-napkin-89521
06/03/2023, 9:39 AM@damp-honey-93158 thank you, I will try to find some information regarding this solution.
2 Views