使用 Resource Manager 模板和 Azure CLI 部署资源Deploy resources with Resource Manager templates and Azure CLI

本文介绍了如何将 Azure CLI 与资源管理器模板配合使用将资源部署到 Azure。This article explains how to use Azure CLI with Resource Manager templates to deploy your resources to Azure. 如果不熟悉部署和管理 Azure 解决方案的概念,请参阅 Azure 资源管理器概述If you aren't familiar with the concepts of deploying and managing your Azure solutions, see Azure Resource Manager overview.

若要运行此示例,请确保已安装最新版本的 Azure CLITo run this sample, make sure you have installed the latest version of the Azure CLI. 若要开始,请运行 az login 以创建与 Azure 的连接。To start, run az login to create a connection with Azure.

此示例在 Bash shell 中正常工作。This sample works in a Bash shell. 有关在 Windows 客户端上运行 Azure CLI 脚本的选项,请参阅在 Windows 上安装 Azure CLIFor options on running Azure CLI scripts on Windows client, see Install the Azure CLI on Windows.

部署范围Deployment scope

可将部署目标设定为 Azure 订阅或订阅中的资源组。You can target your deployment to either an Azure subscription or a resource group within a subscription. 大多数情况下,我们会将以资源组指定为部署目标。In most cases, you'll target deployment to a resource group. 可以使用订阅部署在整个订阅中应用策略和角色分配。Use subscription deployments to apply policies and role assignments across the subscription. 还可以使用订阅部署创建资源组并向其部署资源。You also use subscription deployments to create a resource group and deploy resources to it. 根据部署范围使用不同的命令。Depending on the scope of the deployment, you use different commands.

若要部署到资源组,请使用 az group deployment createTo deploy to a resource group, use az group deployment create:

az group deployment create --resource-group <resource-group-name> --template-file <path-to-template>

若要部署到订阅,请使用 az deployment createTo deploy to a subscription, use az deployment create:

az deployment create --location <location> --template-file <path-to-template>

本文中的示例使用资源组部署。The examples in this article use resource group deployments. 有关订阅部署的详细信息,请参阅在订阅级别创建资源组和资源For more information about subscription deployments, see Create resource groups and resources at the subscription level.

部署本地模板Deploy local template

将资源部署到 Azure 时,执行以下操作:When deploying resources to Azure, you:

  1. 登录到 Azure 帐户Sign in to your Azure account
  2. 创建用作已部署资源的容器的资源组。Create a resource group that serves as the container for the deployed resources. 资源组名称只能包含字母数字字符、句点、下划线、连字符和括号。The name of the resource group can only include alphanumeric characters, periods, underscores, hyphens, and parenthesis. 它最多可以包含 90 个字符。It can be up to 90 characters. 它不能以句点结尾。It can't end in a period.
  3. 将定义了要创建的资源的模板部署到资源组Deploy to the resource group the template that defines the resources to create

模板可以包括可用于自定义部署的参数。A template can include parameters that enable you to customize the deployment. 例如,可以提供为特定环境(如开发环境、测试环境和生产环境)定制的值。For example, you can provide values that are tailored for a particular environment (such as dev, test, and production). 示例模板定义了存储帐户 SKU 的参数。The sample template defines a parameter for the storage account SKU.

Note

在 Azure China 中使用 Azure CLI 2.0 之前,请首先运行 az cloud set -n AzureChinaCloud 更改云环境。Before you can use Azure CLI 2.0 in Azure China, please run az cloud set -n AzureChinaCloud first to change the cloud environment. 如果要切换回全局 Azure,请再次运行 az cloud set -n AzureCloudIf you want to switch back to Global Azure, run az cloud set -n AzureCloud again.

以下示例将创建一个资源组,并从本地计算机部署模板:The following example creates a resource group, and deploys a template from your local machine:

az group create --name ExampleGroup --location "China North"
az group deployment create \
  --name ExampleDeployment \
  --resource-group ExampleGroup \
  --template-file storage.json \
  --parameters storageAccountType=Standard_GRS

部署可能需要几分钟才能完成。The deployment can take a few minutes to complete. 完成之后,会看到一条包含以下结果的消息:When it finishes, you see a message that includes the result:

"provisioningState": "Succeeded",

部署远程模板Deploy remote template

你可能更愿意将 Resource Manager 模板存储在外部位置,而不是存储在本地计算机上。Instead of storing Resource Manager templates on your local machine, you may prefer to store them in an external location. 可以将模板存储在源控件存储库(例如 GitHub)中。You can store templates in a source control repository (such as GitHub). 另外,还可以将其存储在 Azure 存储帐户中,以便在组织中共享访问。Or, you can store them in an Azure storage account for shared access in your organization.

若要部署外部模板,请使用 template-uri 参数。To deploy an external template, use the template-uri parameter. 使用示例中的 URI 从 GitHub 部署示例模板。Use the URI in the example to deploy the sample template from GitHub.

az group create --name ExampleGroup --location "China North"
az group deployment create \
  --name ExampleDeployment \
  --resource-group ExampleGroup \
  --template-uri "https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/101-storage-account-create/azuredeploy.json" \
  --parameters storageAccountType=Standard_GRS

前面的示例要求模板的 URI 可公开访问,它适用于大多数情况,因为模板应该不会包含敏感数据。The preceding example requires a publicly accessible URI for the template, which works for most scenarios because your template shouldn't include sensitive data. 如果需要指定敏感数据(如管理员密码),请以安全参数的形式传递该值。If you need to specify sensitive data (like an admin password), pass that value as a secure parameter. 但是,如果不希望模板可公开访问,可以通过将其存储在专用存储容器中来保护它。However, if you don't want your template to be publicly accessible, you can protect it by storing it in a private storage container. 若要了解如何部署需要共享访问签名 (SAS) 令牌的模板,请参阅部署具有 SAS 令牌的专用模板For information about deploying a template that requires a shared access signature (SAS) token, see Deploy private template with SAS token.

部署失败时,重新部署Redeploy when deployment fails

此功能也称为“出错时回滚”。This feature is also known as Rollback on error. 部署失败时,可以自动重新部署部署历史记录中先前成功的部署。When a deployment fails, you can automatically redeploy an earlier, successful deployment from your deployment history. 若要指定重新部署,请在部署命令中使用 --rollback-on-error 参数。To specify redeployment, use the --rollback-on-error parameter in the deployment command. 如果基础结构部署存在一个已知良好的状态,并且你希望还原到此状态,则此功能非常有用。This functionality is useful if you have got a known good state for your infrastructure deployment and want this to be reverted to. 有许多需要注意的问题和限制:There are a number of caveats and restrictions:

  • 重新部署使用与以前运行它时相同的参数以相同的方式运行。The redeployment is run exactly as it was run previously with the same parameters. 无法更改参数。You can not change the parameters.
  • 以前的部署是使用完整模式运行的。The previous deployment is run using the complete mode. 以前的部署中未包括的任何资源都将被删除,任何资源配置都将设置为以前的状态。Any resources not included in the previous deployment are deleted, and any resource configurations are set to their previous state. 请确保你完全理解部署模式Make sure you fully understand the deployment modes.
  • 重新部署只会影响资源,不会影响任何数据更改。The redeployment only affects the resources, any data changes are not affected.
  • 只有资源组部署支持此功能,订阅级部署不支持此功能。This feature is only supported on Resource Group deployments, not subscription level deployments. 有关订阅级部署的详细信息,请参阅在订阅级别创建资源组和资源For more information about subscription level deployment, see Create resource groups and resources at the subscription level.

若要使用此选项,部署必须具有唯一的名称,以便可以在历史记录中标识它们。To use this option, your deployments must have unique names so they can be identified in the history. 如果没有唯一名称,则当前失败的部署可能会覆盖历史记录中以前成功的部署。If you don't have unique names, the current failed deployment might overwrite the previously successful deployment in the history. 只能将此选项用于根级别部署。You can only use this option with root level deployments. 从嵌套模板进行的部署不可用于重新部署。Deployments from a nested template aren't available for redeployment.

若要重新部署最后一个成功的部署,请将 --rollback-on-error 参数添加为标志。To redeploy the last successful deployment, add the --rollback-on-error parameter as a flag.

az group deployment create \
  --name ExampleDeployment \
  --resource-group ExampleGroup \
  --template-file storage.json \
  --parameters storageAccountType=Standard_GRS \
  --rollback-on-error

若要重新部署某个特定部署,请使用 --rollback-on-error 参数并提供部署名称。To redeploy a specific deployment, use the --rollback-on-error parameter and provide the name of the deployment.

az group deployment create \
  --name ExampleDeployment02 \
  --resource-group ExampleGroup \
  --template-file storage.json \
  --parameters storageAccountType=Standard_GRS \
  --rollback-on-error ExampleDeployment01

指定的部署必须已成功。The specified deployment must have succeeded.

parametersParameters

若要传递参数值,可以使用内联参数或参数文件。To pass parameter values, you can use either inline parameters or a parameter file. 本文中前面的示例显示了内联参数。The preceding examples in this article show inline parameters.

内联参数。Inline parameters

若要传递内联参数,请在 parameters 中提供值。To pass inline parameters, provide the values in parameters. 例如,若要在 Bash shell 中将字符串和数组传递给模板,请使用:For example, to pass a string and array to a template is a Bash shell, use:

az group deployment create \
  --resource-group testgroup \
  --template-file demotemplate.json \
  --parameters exampleString='inline string' exampleArray='("value1", "value2")'

还可以获取文件的内容并将该内容作为内联参数提供。You can also get the contents of file and provide that content as an inline parameter.

az group deployment create \
  --resource-group testgroup \
  --template-file demotemplate.json \
  --parameters exampleString=@stringContent.txt exampleArray=@arrayContent.json

当需要提供配置值时,从文件中获取参数值非常有用。Getting a parameter value from a file is helpful when you need to provide configuration values. 例如,可以为 Linux 虚拟机提供 cloud-init 值For example, you can provide cloud-init values for a Linux virtual machine.

arrayContent.json 格式为:The arrayContent.json format is:

[
    "value1",
    "value2"
]

参数文件Parameter files

你可能会发现,与在脚本中以内联值的形式传递参数相比,使用包含参数值的 JSON 文件更为容易。Rather than passing parameters as inline values in your script, you may find it easier to use a JSON file that contains the parameter values. 参数文件必须是本地文件。The parameter file must be a local file. Azure CLI 不支持外部参数文件。External parameter files aren't supported with Azure CLI.

参数文件必须采用以下格式:The parameter file must be in the following format:

{
  "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
     "storageAccountType": {
         "value": "Standard_GRS"
     }
  }
}

请注意,parameters 部分包含与模板中定义的参数匹配的参数名称 (storageAccountType)。Notice that the parameters section includes a parameter name that matches the parameter defined in your template (storageAccountType). 参数文件包含该参数的值。The parameter file contains a value for the parameter. 此值在部署期间自动传递给模板。This value is automatically passed to the template during deployment. 可以创建多个参数文件,然后为方案传入适当的参数文件。You can create more than one parameter file, and then pass in the appropriate parameter file for the scenario.

复制上面的示例,然后将其另存为名为 storage.parameters.json 的文件。Copy the preceding example and save it as a file named storage.parameters.json.

若要传递本地参数文件,请使用 @ 指定名为 storage.parameters.json 的本地文件。To pass a local parameter file, use @ to specify a local file named storage.parameters.json.

az group deployment create \
  --name ExampleDeployment \
  --resource-group ExampleGroup \
  --template-file storage.json \
  --parameters @storage.parameters.json

参数优先级Parameter precedence

可以在同一部署操作中使用内联参数和本地参数文件。You can use inline parameters and a local parameter file in the same deployment operation. 例如,可以在本地参数文件中指定某些值,并在部署期间添加其他内联值。For example, you can specify some values in the local parameter file and add other values inline during deployment. 如果同时为本地参数文件中的参数和内联参数提供值,则内联值优先。If you provide values for a parameter in both the local parameter file and inline, the inline value takes precedence.

az group deployment create \
  --resource-group testgroup \
  --template-file demotemplate.json \
  --parameters @demotemplate.parameters.json \
  --parameters exampleArray=@arrtest.json

测试模板部署Test a template deployment

若要测试模板和参数值而不实际部署任何资源,请使用 az group deployment validateTo test your template and parameter values without actually deploying any resources, use az group deployment validate.

az group deployment validate \
  --resource-group ExampleGroup \
  --template-file storage.json \
  --parameters @storage.parameters.json

如果未检测到错误,则该命令将返回有关测试部署的信息。If no errors are detected, the command returns information about the test deployment. 需要特别注意的是,error 值为 null。In particular, notice that the error value is null.

{
  "error": null,
  "properties": {
      ...

如果检测到错误,则该命令将返回一条错误消息。If an error is detected, the command returns an error message. 例如,如果为存储帐户 SKU 传递不正确的值,将返回以下错误:For example, passing an incorrect value for the storage account SKU, returns the following error:

{
  "error": {
    "code": "InvalidTemplate",
    "details": null,
    "message": "Deployment template validation failed: 'The provided value 'badSKU' for the template parameter 
      'storageAccountType' at line '13' and column '20' is not valid. The parameter value is not part of the allowed 
      value(s): 'Standard_LRS,Standard_ZRS,Standard_GRS,Standard_RAGRS,Premium_LRS'.'.",
    "target": null
  },
  "properties": null
}

如果模板有语法错误,该命令将返回一个错误,指示它无法分析该模板。If your template has a syntax error, the command returns an error indicating it couldn't parse the template. 该消息会指出分析错误的行号和位置。The message indicates the line number and position of the parsing error.

{
  "error": {
    "code": "InvalidTemplate",
    "details": null,
    "message": "Deployment template parse failed: 'After parsing a value an unexpected character was encountered:
      \". Path 'variables', line 31, position 3.'.",
    "target": null
  },
  "properties": null
}

后续步骤Next steps