Skip to main content

Stack

Stacks allow you to group related workflows together into sets that can be reused across multiple projects and environments. These stacks contain several workflows that execute in sequence, with a high level of interoperability between them. They run in a chain-like order where the output of one workflow serves as the input for the next.

Motivation

  • Modular Deployment: Break down large-scale deployments into manageable, smaller templates while maintaining interdependencies.
  • Automation: Chain workflows to auto-trigger subsequent processes, improving deployment efficiency.
  • Foundation: Each stack is built upon an IaC group, serving as its structural base.
  • Lifecycle Management: Stacks facilitate version updates and template additions, ensuring current and scalable infrastructure.

Stacks Workflow

Stacks operate in a sequential order:

  1. Deployment Sequence: Execute workflows in a specific order using custom actions.
  2. Default Actions: Include default Create and Destroy actions, which can be edited as needed.
  3. Chaining: Outputs from one workflow become inputs for the next, allowing seamless transitions.

Stacks vs. Workflow Groups

Stacks differ from workflow groups in that they maintain a sequence and dependencies between workflows, whereas workflow groups are a collection of independent deployments.

Examples

  • Stack: Sequential deployment of a web server, database, and load balancer with defined dependencies.
  • Workflow Group: Independent management of the same resources without structured interdependencies.