set_pipelinestep was introduced in Concourse v5.8.0. It is considered an experimental feature, until its associated RFC is resolved.
Configures a Concourse pipeline.
Required. The name of the pipeline to configure.
Required. The path to the pipeline's configuration file.
file points at a
.yml file containing the pipeline configuration, which allows this to be tracked with your resources.
The first segment in the path should refer to another source from the plan, and the rest of the path is relative to that source.
For example, if in your plan you have the following
- get: something
something resource provided a
pipeline.yml file, you would set
Optional. A map of template variables to pass to the pipeline config.
For example, a var may be statically passed like so:
plan: - get: my-repo - set_pipeline: configure-the-pipeline file: my-repo/ci/pipeline.yml vars: text: "Hello World!"
This means that any
((vars)) in the pipeline will be resolved using this field. For example, if
my-repo/ci/pipeline.yml looks like
resources: - name: task-image type: docker-image source: repository: my.local.registry:8080/my/image username: ((myuser)) password: ((mypass)) jobs: - name: job plan: - get: task-image - task: do-stuff image: task-image config: platform: linux run: path: echo args: ["((text))"]
...this will resolve
"Hello World!", while
((mypass)) will be resolved in runtime via a credential manager, if it has been configured.
Optional. A list of paths to
.yml files that will be passed to the pipeline config in the same manner as the
--load-vars-from flag to
fly set-pipeline -- this means that if a variable appears in multiple files, the value from a file that is passed later in the list will override the values from files earlier in the list.