Use envVarMappings to run multiple providers with different credentials in the same Pulumi program, no more environment variable conflicts.

The Pulumi blog provides developers with resources, tutorials, and best practices for infrastructure as code (IaC) and cloud-native development using Pulumi's open-source tools. Developers can learn about deploying and managing infrastructure using familiar programming languages such as JavaScript, TypeScript, Python, and Go. Additionally, the blog covers topics such as cloud architecture patterns, multi-cloud deployments, and serverless computing, enabling developers to build and deploy modern cloud applications with ease.

Pulumi

Pulumi v3.220.0 introduces envVarMappings, a new resource option that solves environment variable conflicts when running multiple providers with different credentials. Previously, providers expected fixed environment variable names (like AWS_ACCESS_KEY_ID or ARM_CLIENT_SECRET), making it impossible to configure multiple instances of the same provider targeting different accounts via environment variables. The new feature allows remapping provider environment variables to custom keys, enabling scenarios like multiple Azure providers with different authentication values without writing secrets to state or causing noisy diffs during token rotation.

Introducing envVarMappings for Provider Credentials

Multiple providers or provider instances that expect different authentication values but have the same variable key