title: How do you download *all* pipeline resources in a job?
body: <p>The <code>deployment</code> job automatically downloads all the pipeline resources.  However, standard <code>job</code> does not.  I tried to use <code>- download: current</code>, but that does not download the pipeline resources.</p>
  
  <p>The reason I want to do this is to simulate a deployment for GitOps.  The simulation will include a step that does a <code>git diff</code> that shows the differences for review.</p>
  
  <p>However, I don't see an <code>all</code> or <code>*</code> option in <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&amp;tabs=schema%2Cparameter-schema#download" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&amp;tabs=schema%2Cparameter-schema#download</a></p>
  
  <p>My current workaround is to do a <code>deployment</code> to a "Temp" environment prior to the real <code>deployment</code>.</p>
  
  <p>UPDATE:
  Here's an example of what I have tried </p>
  
  <pre><code>resources:
    pipelines:
      - pipeline: auth
        project: myproj
        source: auth CI
        trigger:
          branches:
            include:
              - master
  ...
      jobs:
        - job: diagnostics
          displayName: Job Diagnostics
          steps:
            - checkout: self
            # - download: 
            - task: DownloadPipelineArtifact@2
              displayName: 'Download Pipeline Artifact'
              inputs:
                path: $(Build.SourcesDirectory)
            - bash: |
                env | sort
              displayName: Display environment variables
            - bash: |
                pwd
              displayName: Present working directory
            - bash: |
                find $(Pipeline.Workspace) -type f -print
              displayName: Display files
  </code></pre>
  
  <p>UPDATE:
  Another approach I was mulling is to create a pipeline that creates another pipeline.  That way the list of pipeline resources does not need to be Azure Pipeline YAML, it could be a CSV or a simplified YAML that I transform in which case I can generate</p>
  
  <pre><code>resources:
    pipelines:
      - pipeline: pipelineAlias1
        project: myproj
        source: auth CI
        branch: master
        trigger:
          branches:
            include:
              - master
  
      - pipeline: pipelineAlias2
        project: myproj
        source: auth CI
        branch: master
        trigger:
          branches:
            include:
              - master
  ...
  job:
    steps:
     - download: pipelineAlias1
     - download: pipelineAlias2
  
  </code></pre>
  
  <p>and then set that up as another Azure pipeline to execute when updated.  </p>