Azure DevOps中无标记资源时如何将Stage设为可选？

我有如下YAML结构，部分环境缺少SQL相关架构组件，因此不存在带有sql标记的虚拟机资源。我想把这类SQL部署阶段设为可选——比如关闭无标记资源的错误提示、按环境名称设置执行条件，但始终无法实现。看起来资源检查是在我的条件评估之前执行的，或者我引用变量的方式有问题？

parameters:
  - name: stages 
    type: object
    default:
      - stage: CI
        dependsOn: Build
        stageName: CI
      - stage: DEV
        dependsOn: DeployCI
        stageName: DEV
        ...
        ...
  - ${{ each stage in parameters.stages }}:   
    - stage: Deploy${{ stage.stageName }}
      displayName: Deploy to ${{ stage.stage }}
      variables: 
        - group: '${{ stage.stage }}'                 
        - group: 'CRIMS.Config.${{ stage.stage }}'    
      dependsOn: ${{ stage.dependsOn }}
      condition: notIn(variables['stage.stageName'], 'CI')               
      jobs:
        - deployment: DeploySQL
          workspace:
            clean: all
          displayName: Deploy SQL to ${{stage.stage}}
          environment:
            name: ${{stage.stage}}
            resourceType: virtualMachine
            tags: sql
       strategy:

1. 用模板表达式跳过SQL作业 #

环境资源检查是在作业初始化阶段执行的，而condition是运行时才评估，所以得用模板层面的${{ if }}条件来决定是否生成这个作业，从根源避免资源检查报错。

可以给每个stage参数添加enableSqlDeployment字段，明确控制是否启用SQL部署：

parameters:
  - name: stages 
    type: object
    default:
      - stage: CI
        dependsOn: Build
        stageName: CI
        enableSqlDeployment: false # CI环境关闭SQL部署
      - stage: DEV
        dependsOn: DeployCI
        stageName: DEV
        enableSqlDeployment: true # DEV环境开启SQL部署
        ...
        ...
  - ${{ each stage in parameters.stages }}:   
    - stage: Deploy${{ stage.stageName }}
      displayName: Deploy to ${{ stage.stage }}
      variables: 
        - group: '${{ stage.stage }}'                 
        - group: 'CRIMS.Config.${{ stage.stage }}'    
      dependsOn: ${{ stage.dependsOn }}
      condition: notIn(variables['stage.stageName'], 'CI')               
      jobs:
        # 仅当enableSqlDeployment为true时才生成SQL部署作业
        ${{ if eq(stage.enableSqlDeployment, true) }}:
        - deployment: DeploySQL
          workspace:
            clean: all
          displayName: Deploy SQL to ${{stage.stage}}
          environment:
            name: ${{stage.stage}}
            resourceType: virtualMachine
            tags: sql
          strategy:
            runOnce:
              deploy:
                steps:
                  - script: echo Deploying SQL...

2. 关闭环境资源标记检查 #

如果不想完全跳过作业，只是想避免无标记资源的报错，可以在环境配置中关闭资源标记检查，同时在步骤里添加判断逻辑，确保只有存在资源时才执行部署：

- deployment: DeploySQL
          workspace:
            clean: all
          displayName: Deploy SQL to ${{stage.stage}}
          environment:
            name: ${{stage.stage}}
            resourceType: virtualMachine
            tags: sql
            resourceTagsCheck: false # 关闭资源标记检查
          strategy:
            runOnce:
              deploy:
                steps:
                  # 先检查是否存在符合条件的资源，不存在则跳过
                  - script: |
                      # 这里写检查SQL资源的逻辑，比如调用Azure CLI查询虚拟机标记
                      az vm list --resource-group <你的资源组> --tag sql --query "[].name" --output tsv
                    displayName: Check SQL resources exist
                    continueOnError: true
                    name: CheckSQL
                  - script: echo Deploying SQL...
                    displayName: Execute SQL deployment
                    condition: ne(steps.CheckSQL.outputs.stdout, '')

3. 结合参数与运行时条件 #

如果需要更灵活的动态控制，可以通过变量组或参数传入开关，结合运行时条件和资源检查关闭：

- deployment: DeploySQL
          workspace:
            clean: all
          displayName: Deploy SQL to ${{stage.stage}}
          # 运行时判断是否执行作业
          condition: eq(variables['EnableSQLDeployment'], 'true')
          environment:
            name: ${{stage.stage}}
            resourceType: virtualMachine
            tags: sql
            resourceTagsCheck: false
          strategy:
            runOnce:
              deploy:
                steps:
                  - script: echo Deploying SQL...

其中EnableSQLDeployment变量可以在对应环境的变量组中定义，或者直接作为stage参数传入。

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