Brainboard's documentation
Go to the app ↗
  • Welcome
  • Getting started
    • Fast track
    • Start with a template
    • Start with AI
    • Use cases videos
    • Brainboard philosophy
  • Cloud design
    • Left bar
      • Cloud resources
      • Input & output
    • Design area
      • Node
      • ID card
      • Connectors
      • Versioning
      • Graphical options
    • One action
    • Code Edition
  • Data
    • Data structure
      • Project
      • Environment
      • Cloud architecture
        • Terraform files
        • Readme file
        • Architecture Synchronization
        • Remote backend
      • Template
    • Cloud providers
      • Supported cloud providers
      • Customize provider configuration
      • Unsupported cloud providers
    • Terraform / OpenTofu
      • Modules
        • Module
        • Import modules
        • Manage module
        • Terraform registry credentials
        • Use modules
    • Disaster recovery
  • Automation
    • CI/CD engine
    • Supported plugins
      • Terraform
      • Security
        • Trivy
        • Tfsec
        • Terrascan
        • OPA
        • Checkov
      • Infracost
      • Notifications
        • Email
        • Slack
        • Microsoft Teams
      • Webhooks
    • Pipelines
    • Workflow templates
    • Drift detection
      • Types of drift
      • Remediation
    • Self-Hosted Runner
      • Deploy runner with Kubernetes
      • Deploy runner with docker-compose
  • Settings
    • Overview
    • Authentication
      • Login into Brainboard
      • Single sign-on (SSO)
    • Account management
    • Organization
    • Members
    • Teams
    • Roles & Permissions (RBAC)
      • Level of access
      • Organization RBAC
      • Project RBAC
    • Integrations
      • Git configuration
        • GitHub
        • Azure DevOps (ADO)
        • Bitbucket
        • GitLab
        • How to use
      • Cloud providers
        • AWS
        • Azure
        • GCP
        • OCI
  • Security
    • Data managed by Brainboard
    • SOC 2 Type II
    • Role Based Access Control
  • Help & FAQ
    • Shortcuts
    • FAQ
    • Migration
      • Import from cloud provider
    • Support
    • Glossary
  • Changelog
Powered by GitBook
On this page
  • Description
  • Create template
  • Clone template
  • Delete template
  • Best practices

Was this helpful?

Edit on GitHub
  1. Automation

Workflow templates

PreviousPipelinesNextDrift detection

Last updated 8 months ago

Was this helpful?

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 don't 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 the deploy tab within your architecture

  2. Click on Templates in the left menu

  3. Hover the workflow template you want to delete

  4. Click on Create workflow from template

  5. Confirm the action

Delete template

To delete a template:

  1. Go the deploy tab within your architecture

  2. Click on Templates in the left menu

  3. Hover the workflow template you want to delete

  4. Click on Delete template

  5. Confirm the action to permanently delete it

Deleting a workflow template cannot be undone.

Best practices

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

  2. Create as many workflows that 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 (team's email) in the approvals field in tasks before creating templates to not be dependent on specific persons.

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

Workflow templates
Clone workflow template
Delete workflow template