Azure / Azure/azure-quickstart-templates
Discuss the best practice to support different environment
- Dominant language
- Bicep
- Stars
- 14.9k
- Forks
- 16.2k
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 6
Description
Hi community,
I notice that, almost all templates don't support other environment than Global Azure. However, Azure has several different environments: `Azure`, `AzureChina`, `AzureUSGovernment`, `AzureGermanCloud`. In each environment, some endpoints are different. Reference: https://github.com/Azure/azure-sdk-for-node/blob/master/runtime/ms-rest-azure/lib/azureEnvironment.js
**Does community has an advice or best practice about how to deal with these different environments?**
This is what I do: [bosh-setup](https://github.com/Azure/azure-quickstart-templates/blob/master/bosh-setup/azuredeploy.json).
In `bosh-setup`, we use a parameter `environment` for `Azure` and `AzureChinaCloud`. It works fine with Azure CLI.
But for the Portal experience, we need to add a button to deploy the template. We are working on it, so that we'll have two buttons, one for Azure, one for AzureChinaCloud. Any suggestions?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the referenced runtime-ms-rest-azure/lib/azureEnvironment.js and the bosh-setup/azuredeploy.json example. Compare how the environment parameter works with Azure CLI and how Portal deployment buttons would need to cover Azure and AzureChinaCloud. Done means reaching and documenting a clear recommendation for supporting the listed Azure environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100