Workflow templates

Description

Workflow templates is a library of templates that contains all workflow scenarios that you build once and use everywhere.

This is a great way to standardize your deployment process without reinventing the wheel, as it allows you to stay DRY (don't repeat yourself) even at the workflow level. You no longer need to copy and paste YAML files and manually change them for every architecture.

Create template

To create a new template, refer to the page: create workflow template. It contains all the details.

Clone template

To clone a template and add it to your architecture:

1. Go to the CI/CD tab in the top navigation bar, within your architecture.

2. Click on Templates in the left menu.

3. Hover the workflow template you want to clone, and click on the copy icon at the bottom-right corner of the template thumbnail. Its tooltip will display Create workflow from template when hovered over.

4. Confirm the action by clicking the Use template button on the Create workflow from template confirmation modal.

Delete template

To delete a template:

1. Go to the CI/CD tab in the top navigation bar, within your architecture.

2. Click on Templates in the left menu.

3. Hover the workflow template you want to clone, and click on the bin icon at the bottom-right corner of the template thumbnail. Its tooltip will display Delete template when hovered over.

4. Confirm the action by clicking the Delete button on the Workflow template deletion confirmation modal.

Deleting a workflow template cannot be undone.

Best practices

1. It's a good practice to include security checks as part of your process. Users will get used to it and will help you raise awareness about infrastructure security.

2. Create as many workflows as you can to represent your deployment scenarios. It helps your team members quickly pick the right one.

3. Always add a description when you create a template.

4. Put generic emails (the team's email) in the approvals field in tasks before creating templates so they are not dependent on specific persons.

5. You can use naming conventions for workflows, especially if you have workflows for different teams.