In a nutshell:
Engineers describe their infrastructure as code with their favorite IaC tool.
They push their code to their VCS system.
A Spacelift stack is created against that VCS repo. This stack catches the change and triggers a tracked run.
Based on the stack settings, this may be applied automatically, or it may require a manual intervention.
Infrastructure changes are applied in your provider.
In Spacelift, stacks are responsible for configuring and deploying your workflow. You can have your choice of VCS provider and backend (Terraform, OpenTofu, etc.), configure versions, optionally configure what happens before and after every runner phase β and even attach cloud integrations for short-lived credentials, policies, and contexts.
Use policy as code to define the types of resources your workflows can create, the resource parameters, the number of approvals required for a run, what happens when a PR is open against a branch, and where to send notifications. Attach policies from the following categories to as many stacks as you want:
Add commands between your runner phases, bring your own image, or even configure the default workflow commands. This flexibility enables easy integration with any third-party tool. You can even define policies for workflows via custom inputs, and you never have to compromise.
Use stack dependencies to easily configure your EC2 instances and K8s clusters. Share outputs between dependent stacks. Nest those dependencies to trigger runs on child stacks when the parent stack finishes a run successfully.Β Transform your monolith deployment into multiple micro-deployments, making it easy to identify where problems arise. Your workflow potential is limitless!