如何防止 Microsoft.Automation/automationAccounts/Compilationjobs 在 ARM 部署中始终 运行？

Question

下面是我的ARM模板，它是嵌套在更大的ARM模板中的模板。出于某种原因，每次部署时 DSC 编译作业总是 运行。如果之前已经是 运行，我预计它不会是 运行。我如何控制这种行为？我尝试使用 "incrementNodeConfigurationBuild": "false" 但它没有成功。

 {
      "name": "WorkerNodeDscConfiguration",
      "type": "Microsoft.Resources/deployments",
      "apiVersion": "2017-05-10",
      "resourceGroup": "[parameters('automationAccountRGName')]",
      "dependsOn": [],
      "properties": {
        "mode": "Incremental",
        "template": {
          "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
          "contentVersion": "1.0.0.1",
          "resources": [
            {
              "apiversion": "2015-10-31",
              "location": "[reference(variables('automationAccountResourceId'), '2018-01-15','Full').location]",
              "name": "[parameters('automationAccountName')]",
              "type": "Microsoft.Automation/automationAccounts",
              "properties": {
                "sku": {
                  "name": "Basic"
                }
              },
              "tags": {},
              "resources": [
                {
                  "name": "workernode",
                  "type": "configurations",
                  "apiVersion": "2018-01-15",
                  "location": "[reference(variables('automationAccountResourceId'), '2018-01-15','Full').location]",
                  "dependsOn": [
                    "[concat('Microsoft.Automation/automationAccounts/', parameters('AutomationAccountName'))]"
                  ],
                  "properties": {
                    "state": "Published",
                    "overwrite": "false",
                    "incrementNodeConfigurationBuild": "false",
                    "Source": {
                      "Version": "1.2",
                      "type": "uri",
                      "value": "[parameters('WorkerNodeDSCConfigURL')]"
                    }
                  }
                },
                {
                  "name": "[guid(resourceGroup().id, deployment().name)]",
                  "type": "Compilationjobs",
                  "apiVersion": "2018-01-15",
                  "tags": {},
                  "dependsOn": [
                    "[concat('Microsoft.Automation/automationAccounts/', parameters('AutomationAccountName'))]",
                    "[concat('Microsoft.Automation/automationAccounts/', parameters('AutomationAccountName'),'/Configurations/workernode')]"
                  ],
                  "properties": {
                    "configuration": {
                      "name": "workernode"
                    },
                    "incrementNodeConfigurationBuild": "false",
                    "parameters": {
                      "WebServerContentURL": "[parameters('WebServerContentURL')]"
                    }
                  }
                }
              ]
            }
          ]
        }
      }
    }

Answer 1

简而言之，据我所知，您应该可以使用 'condition' 来控制此行为。

详细解释一下，每次部署时 DSC 编译作业资源总是 运行，因为当我们在 ARM 模板中使用 DSC 编译作业资源（即 Microsoft.Automation/automationAccounts/compilationjobs）时，恕我直言，它在后面做的是，基本上点击 DSC 配置的 'Compile' 按钮。

如果你点击 'Compile' 按钮，即使它已经编译了作业，作业的编译也会发生。您也可以手动检查相同的部分。

所以 AFAIK 这就是每次部署时编译作业总是 运行ning 的原因。

您可以做的是，使用 'condition' 更新您的 ARM 模板（有关详细信息，请参阅 https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-templates-resources#condition and https://docs.microsoft.com/en-us/azure/architecture/building-blocks/extending-templates/conditional-deploy) and then wrap your template with below sample piece of PowerShell code that would determine if the Compilation of job for particular DSC configuration is done already and then deploy the template by passing inline parameter value or by updating condition parameter in parameters template file with new or existing value accordingly. (For more information, refer https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-template-deploy#pass-parameter-values）

$DscCompilationJob = Get-AzAutomationDscCompilationJob -AutomationAccountName AUTOMATIONACCOUNTNAME -ResourceGroupName RESOURCEGROUPNAME|Sort-Object -Descending -Property CreationTime|Select -First 1| Select Status
$DscCompilationJobStatus = $DscCompilationJob.Status
if ($DscCompilationJobStatus -ne "Completed"){
    $DscCompilationJobStatusInlineParameter = "new"
    New-AzResourceGroupDeployment -Name ExampleDeployment -ResourceGroupName testgroup -TemplateFile TEMPLATEFILEPATH\demotemplate.json -exampleString $DscCompilationJobStatusInlineParameter
    #or update condition parameter in parameters template file with new value accordingly and use below command to deploy the template
    New-AzResourceGroupDeployment -Name ExampleDeployment -ResourceGroupName ExampleResourceGroup -TemplateFile TEMPLATEFILEPATH\demotemplate.json -TemplateParameterFile TEMPLATEFILEPATH\demotemplate.parameters.json
}else{
    $DscCompilationJobStatusInlineParameter = "existing"
    New-AzResourceGroupDeployment -Name ExampleDeployment -ResourceGroupName testgroup -TemplateFile TEMPLATEFILEPATH\demotemplate.json -exampleString $DscCompilationJobStatusInlineParameter
    #or update condition parameter in parameters template file with existing value accordingly and use below command to deploy the template
    New-AzResourceGroupDeployment -Name ExampleDeployment -ResourceGroupName ExampleResourceGroup -TemplateFile TEMPLATEFILEPATH\demotemplate.json -TemplateParameterFile TEMPLATEFILEPATH\demotemplate.parameters.json
}

关于 incrementNodeConfigurationBuild 属性，恕我直言，这个 属性 只是关于是否需要创建新的节点配置版本，即当增量节点配置构建设置为 false 时, 它不会通过创建名称为 CONFIGNAME[<2>] 的新节点配置来覆盖早期的现有节点配置（版本号根据已经存在的现有版本号递增）。

希望对您有所帮助！！干杯！！ :)