No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hi all,
I'm working with the azure-native provider using the pulumi Java SDK. It works too well :slightly_smiling_face:

I have two stacks called `development` and `production` . I also have two Azure subscriptions called `development` and `production` . I want the stack for each environment to provision resources in its corresponding subscription.

I have `Pulumi.development.yaml` and `Pulumi.production.yaml` config files. I noticed that even if I don't do `pulumi config set azure-native:subscriptionId <subscription id>` then pulumi works just fine for both stacks.

This is surprising because I would expect pulumi / native axure provider to fail or use the default az account, which in my case is set to `development`. However, both the `dvelopment` and `peoduction` stacks work well (when I do pulumi refresh I get no changes for both except for a minor etag on a vnet, which changes all the time).

This is a little concerning because if pulumi uses some magic to decide which subscription to target then this is a cause for concern. Can someone explain what's going on? am I missing something or misunderstanding something?