Updated Azure CLI command usage as az is now the CLI2.0 command and on systems with both installed could be confusing as CLI 2.0 does not have deployment from templates yet. I also added the parameters file path to feed in the parameters file during deployment.
This commit is contained in:
Eddie Villalba 2016-11-01 08:16:59 -04:00 коммит произвёл GitHub
Родитель 9c9ca03082
Коммит 2a19d6840c
1 изменённых файлов: 8 добавлений и 6 удалений

Просмотреть файл

@ -82,18 +82,19 @@ Generated templates can be deployed using
### Deploying with Azure CLI
```bash
$ az login
$ azure login
$ az account set --name "<SUBSCRIPTION NAME OR ID>"
$ azure account set --name "<SUBSCRIPTION NAME OR ID>"
$ az group create \
$ azure group create \
--name="<RESOURCE_GROUP_NAME>" \
--location="<LOCATION>"
$ az group deployment create \
$ azure group deployment create \
--name="<DEPLOYMENT NAME>" \
--resource-group="<RESOURCE_GROUP_NAME>" \
--template-file="./_output/<INSTANCE>/azuredeploy.json"
--template-file="./_output/<INSTANCE>/azuredeploy.json" \
--parameters-file="./_output/<INSTANCE>azuredeploy.parameters.json"
```
### Deploying with Powershell
@ -110,6 +111,7 @@ New-AzureRmResourceGroup `
New-AzureRmResourceGroupDeployment `
-Name <DEPLOYMENT_NAME> `
-ResourceGroupName <RESOURCE_GROUP_NAME> `
-TemplateFile _output\<INSTANCE>\azuredeploy.json
-TemplateFile _output\<INSTANCE>\azuredeploy.json `
-TemplateParameterFile _output\<INSTANCE>\azuredeploy.parameters.json
```