Azure CLI Context, Not Env Files, Should Define Dev, Staging and Prod Isolation
The article argues that teams often rely on many near-identical .env example files, which tend to drift and leave different people and tools working from conflicting configuration. It proposes treating the Azure CLI context, meaning subscription, resource group and deploy identity, as the real isolation boundary, since a correct file against the wrong subscription still deploys to the wrong environment. The recommended approach is to keep one canonical set of stage templates in Git that document setting names and non-secret defaults, with no embedded secrets. Application secrets should live in Key Vault and App Settings, and deploy scripts should print and verify the active subscription and resource group before making changes. Shared product code can be used across POC and MVP stages as long as each keeps separate resource groups and stage settings.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in