Azure Pipeline传递stageList参数至扩展模板遇错误求助

Hey there! Let's break down why you're hitting that unexpected "task" error even though you didn't use the keyword directly.

The root issue is that Azure Pipelines treats shortcuts like bash and script as syntactic sugar for actual tasks under the hood. For example:

• bash maps to the Bash@3 task
• script maps to the CmdLine@2 task

When the pipeline parses your YAML, these shortcuts get converted into full task definitions with a task property—so your template ends up encountering this keyword even though you didn't write it explicitly. Your current loop logic also breaks the pipeline structure by iterating over every key-value pair in a step, which confuses the parser.

Here's a fixed template that properly validates compliance #

This version preserves the original stage/job structure, correctly identifies task types (including shortcuts), and blocks unapproved tasks like CmdLine@2:

parameters:
- name: cdstages
  type: stageList
  default: []

stages:
- ${{ each stage in parameters.cdstages }}:
  # Recreate the stage with its original name and pool
  - stage: ${{ stage.name }}
    pool: ${{ stage.pool }}
    jobs:
    - ${{ each job in stage.jobs }}:
      # Recreate the job with its original name
      - job: ${{ job.name }}
        steps:
        - ${{ each step in job.steps }}:
          # Determine the actual task type (handle shortcuts)
          ${{ assign 'taskType' = step.task }}
          ${{ if ne(step.bash, '') }}:
            ${{ assign 'taskType' = 'Bash@3' }}
          ${{ if ne(step.script, '') }}:
            ${{ assign 'taskType' = 'CmdLine@2' }}
          
          # Compliance check: Block unapproved tasks (e.g., CmdLine@2)
          ${{ if eq(taskType, 'CmdLine@2') }}:
            script: echo "ERROR: Task type '${{ taskType }}' is not approved by the compliance team!" && exit 1
            displayName: 'Compliance Violation Detected'
          ${{ else }}:
            # Keep the approved step as-is
            ${{ step }}

How this works: #

1. Preserves valid structure: We explicitly recreate each stage, job, and step using their original properties, so the pipeline maintains valid YAML syntax.
2. Detects all task types: We map shortcut commands like bash/script to their actual task IDs, ensuring we can check against your compliance list regardless of how the step is written.
3. Blocks unapproved tasks: If a step uses CmdLine@2 (or any other unapproved task), it gets replaced with an error step that fails the pipeline and clearly explains the violation.

You can easily extend this by adding more approved tasks to the conditional logic—just add additional or clauses to the check if you want to allow more task types.

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