Using Pipeline Templates

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.

  Save a pipeline template to Spinnaker to make it available to developers.

• Use the <code>spin</code> 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 .

Enable Pipeline Templates

Enable the pipeline templates feature in Spinnaker.

Create a Pipeline Template

Create and parameterize a pipeline template from an existing pipeline.

Inherit from a Template or Override It

Inherit or override template features in your pipeline.

Create a Pipeline from a Template

Create pipelines based on a template.

Visualize a Hydrated Pipeline

Visualize a pipeline created from a pipeline template without actually instantiating one.

Last modified May 7, 2021: docs(migration): fix imgs and links (9a18ce6)