Skip to main content

Spacelift Integration (Deprecated)

Deprecated

The Atmos Spacelift integration is no longer promoted for new projects. Use the native CI integration for new automation. This page is retained for teams that already manage Spacelift resources with Atmos.

Component ordering is configured with dependencies.components, not settings.depends_on.

This legacy integration provisions Spacelift resources from Atmos stack configurations through the Cloud Posse Terraform module.

Cloud Posse provides Terraform components for provisioning Spacelift worker pools and Spacelift stacks.

Stack Configuration​

Existing Spacelift installations can continue to use settings.spacelift:

components:
  terraform:
    example:
      settings:
        spacelift:
          workspace_enabled: true
          administrative: true
          autodeploy: true
          before_init: []
          component_root: components/terraform/example
          description: Example component
          stack_destructor_enabled: false
          worker_pool_name: null
          policies_enabled: []
          administrative_trigger_policy_enabled: false
          policies_by_id_enabled:
            - trigger-administrative-policy

OpenTofu Support​

Spacelift supports OpenTofu globally or per component:

settings:
  spacelift:
    terraform_workflow_tool: OPEN_TOFU
components:
  terraform:
    my-component:
      settings:
        spacelift:
          terraform_workflow_tool: OPEN_TOFU

Component Dependencies​

Use the current dependency format for Spacelift stack ordering as well as local and native-CI execution:

components:
  terraform:
    app:
      dependencies:
        components:
          - name: network
          - name: shared-services
            stack: tenant1-ue2-prod

For the complete dependency reference and migration guidance, see Component Dependencies.