Skip to main content

Stack

Stacks enable you to organize and execute multiple related workflows in a defined sequence. These workflows are designed to work together, where the output of one workflow is automatically passed as the input for the next. This structure ensures efficient, automated, and interconnected deployment processes across various projects and environments.

How Stacks Work​

Stacks run workflows in a specific, step-by-step order to achieve seamless integration. Here’s how they operate:

  1. Sequential Execution: Workflows are executed one after another in a predefined order, ensuring smooth transitions between tasks.
  2. Default Actions: Each stack includes default Create and Destroy actions for deployment and cleanup, which you can customize as needed.
  3. Output Chaining: The output from one workflow is automatically used as input for the next workflow, eliminating manual intervention and ensuring continuity.

Stacks vs. Workflow Groups​

While both stacks and workflow groups help manage workflows, they serve different purposes:

  • Stacks:

    • Designed for workflows that depend on each other.
    • Maintain a specific order of execution.
    • Ideal for scenarios requiring interdependent resources (e.g., deploying a VPC, EKS cluster, and managed nodes sequentially).

  • Workflow Groups:

    • Collections of independent workflows that do not rely on each other.
    • No predefined execution order.
    • Useful for managing workflows without dependencies, like testing different infrastructure setups.

Example Scenarios​

  • Stack: Deploying a web application in a sequence:

    1. Create a Virtual Private Cloud (VPC).
    2. Deploy a Kubernetes cluster in the VPC.
    3. Add managed node groups to the cluster.
    4. Deploy an Nginx service on the cluster.

  • Workflow Group: Independently managing resources:

    1. Deploying a database in one workflow.
    2. Testing a web server in another workflow.
    3. Each workflow runs separately, without dependency on the others.