Bicep重新部署时LAW资源计划冲突，需实现幂等部署

问题原因 #

重新部署时的计划冲突主要来自Microsoft.OperationsManagement/solutions资源，这类资源关联的Log Analytics Workspace（LAW）定价计划在已部署后，增量部署模式下会尝试更新资源，若计划参数与现有资源不一致或重复创建，就会触发报错。

解决方案 #

通过给冲突资源添加存在性判断条件，仅在资源未创建时执行部署，实现增量模式下的幂等效果，不影响其他已存在资源：

1. 处理Operations Management Solutions
   对每个要部署的解决方案，用exists()函数检查是否已存在，不存在才执行部署：

   param parPcLawSolutions array = [   
     'AzureActivity'
     'ChangeTracking'
     'Security'
   ]
   param lawName string
   param location string
   
   resource law 'Microsoft.OperationalInsights/workspaces@2022-10-01' = {
     name: lawName
     location: location
     properties: {
       sku: {
         name: 'PerGB2018' // 保持与现有LAW一致的SKU，避免修改计划
       }
     }
   }
   
   resource lawSolutions 'Microsoft.OperationsManagement/solutions@2015-11-01-preview' = [for solution in parPcLawSolutions: {
     condition: !exists(resourceId('Microsoft.OperationsManagement/solutions', '${solution}(${lawName})'))
     name: '${solution}(${lawName})'
     location: location
     properties: {
       workspaceResourceId: law.id
     }
     plan: {
       name: '${solution}(${lawName})'
       publisher: 'Microsoft'
       product: 'OMSGallery/${solution}'
       promotionCode: ''
     }
   }]
   

2. 处理Log Analytics Workspace本身
   若不需要修改现有LAW的配置，可添加条件仅在资源不存在时创建：

   resource law 'Microsoft.OperationalInsights/workspaces@2022-10-01' = {
     condition: !exists(resourceId('Microsoft.OperationalInsights/workspaces', lawName))
     name: lawName
     location: location
     properties: {
       sku: {
         name: 'PerGB2018'
       }
       // 其他必要属性
     }
   }
   

   如需兼容现有LAW的SKU，可通过reference函数获取现有配置：

   var existingLawSku = exists(resourceId('Microsoft.OperationalInsights/workspaces', lawName)) ? reference(resourceId('Microsoft.OperationalInsights/workspaces', lawName), '2022-10-01').sku.name : 'PerGB2018'
   
   resource law 'Microsoft.OperationalInsights/workspaces@2022-10-01' = {
     name: lawName
     location: location
     properties: {
       sku: {
         name: existingLawSku
       }
     }
   }
   

3. 处理Linked Services资源
   同样添加存在性判断，避免重复创建：

   resource linkedService 'Microsoft.OperationalInsights/workspaces/linkedServices@2020-08-01' = {
     condition: !exists(resourceId('Microsoft.OperationalInsights/workspaces/linkedServices', lawName, 'AzureSecurityCenter'))
     parent: law
     name: 'AzureSecurityCenter'
     properties: {
       resourceId: '/subscriptions/{subscriptionId}/providers/Microsoft.Security/securityCenters/default'
     }
   }
   

核心逻辑 #

利用Bicep的exists()函数检测目标资源是否已存在，通过condition控制资源部署的执行时机，确保增量模式下仅创建缺失的资源，不修改或重复创建已存在的资源，从而避免计划冲突，实现幂等部署。

内容的提问来源于stack exchange，提问作者kpgkondo