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

Hey <@U064ED0G799>! I am checking in with the team regarding feedback on this topic.

In the meantime, if your concern is mainly around configuring/maintaining environment variables locally, then this may be a great use case for implementing <https://www.pulumi.com/docs/pulumi-cloud/esc/|Pulumi ESC>. We have some helpful content around:

• <https://www.pulumi.com/docs/pulumi-cloud/oidc/azure/|Configuring OIDC with Azure> and
• <https://www.pulumi.com/docs/pulumi-cloud/esc/environments/#projecting-environment-variables|Projecting Environment Variables in Pulumi ESC>
You can configure your environment so that those OIDC environment variables are dynamically generated and consumed when you run `pulumi up`

Thank you <@U05HAMJV8J3>, ESC is part of Pulumi cloud, right? Unfortunately, we can't use that at the moment.

The problem with the environment variables is that I need to configure two Azure native providers at the same time, both with different OIDC credentials, which means that I can't use the environment variables to configure the providers (both providers would use the same credentials, which I can't use). I hope that makes sense

Thank you for reporting this! I believe this was an oversight. I’ve raised issue <https://github.com/pulumi/pulumi-azure-native/issues/2873> and started working on the fix.

awesome, thank you! I would've raised an issue myself but I wasn't sure if it was intentional and I'd missed something