Menu

1 / 5

Env Isolation: How Do You Handle Dev/Staging/Prod with Azure CLI and Subscriptions?

DEV Community: azure·Sai Prudhvi Neelakantam·about 1 hour ago
#4eS5NvgR
#devtoazure#devto#dev#azure#deploy
Reading 0:00
15s threshold

I used AI tools to help draft and edit this post. I checked the facts and the wording, and the original lives at geekindata.com . The diagrams are on that page.

Files describe; CLI selects

Key takeaways

Treat Azure CLI subscription, resource group, and identity as the isolation boundary.

Keep a canonical env template set in Git; delete near-duplicate examples.

Secrets live in Key Vault / App Settings; templates document names only.

Deploy scripts print and verify az account show and target RG before mutate.

Share product code across POC/MVP; keep separate resource groups and stage settings.

One path map for humans and agents; fail closed when required settings are missing.

Six nearly identical .env.example files feel thorough. They guarantee drift. Someone updates three. Prod still reads the fourth. Agents and humans resolve different paths. The repo looks configured.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.