Using Pipeline Templates

Pipeline Templates help you standardize and distribute reusable Pipelines across your team or among multiple teams.

You can share these templates with your teams within a single application, across different applications, or even across different deployments of Spinnaker itself.

Templates can be managed using Spin or the UI. To manage templates through the UI, enable the requisite feature flag: hal config features edit --managed-pipeline-templates-v2-ui true

Note: You can use spin CLI to manage pipelines and pipeline templates, but first you need to install it.

Note: You first need to enable the feature if you haven’t done it yet.

Structure of a pipeline template

The underlying structure of a pipeline template is very close to the pipeline JSON configuration format, viewable in the Deck UI. But it includes information about the variables the template uses.

The things you can do with pipeline templates

• Create a template based on an existing pipeline.

• Share the template with one or more teams of developers using Spinnaker.

  To save a pipeline template to Spinnaker is to make it available to developers. It’s a good idea though to communicate to the team what templates are available.

• Use the spin CLI to plan how to parameterize the template, by visualizing a hydrated pipeline.

• Create a pipeline based on a template.

• Override template definitions in your pipeline.

• List and get pipeline templates.