Only space_admin can create stack depencies.

You are unable to create stack dependencies without space admin

Allow merging multiple stack notifications into common GitHub PR comment

We sometimes get PRs which affect many different Stacks. Because each Stack posts an individual comment with the proposed run status, the PR conversation section can become bloated and basically unusable. Also, we have hit GitHub API rate limits and the comments may have contributed here. We would like there to be an option to merge proposed runs into a single PR comment which would gather all proposed runs for given PR. We keep comment content quite short, so the GitHub comment character limit should not be an issue.

Default worker pool at space or organization level

It would be helpful to set a private workerpool as the default for all stacks organization-wide.

Add template data sources to Terraform provider

Add data sources for working with templates in the Terraform provider, such as spacelift_templates to list templates and spacelift_template_version_by_name to resolve a version by name (for example 1.0.0).

Auto-release stale Terraform state locks on run failure

When a run fails unexpectedly, stale Terraform state locks are sometimes left behind. Request to have this condition detected and automatically clean up locks that were created as part of a run.

Sharing private worker pools across spaces without inheritance

We would like the ability to share private worker pools across spaces without requiring space inheritance to be enabled. Ideally, this would support sharing between sibling spaces, in a similar way to how modules can currently be shared.

Expose Busy / Queue length Worker Pool Metrics

I would like to be able to systematically monitor our worker pool to get quantitative data on our internal developer experience as our engineers all share the worker pool to run their IaC. I would like to use those metrics to improve decision making on the number of workers we need for our organizations needs.

Module registry: add version lifecycle states with optional sunset date

“Mark version as bad” is informational only. Enterprise customers need a structured lifecycle so module authors can deprecate versions with a grace period and then block unsupported versions without maintaining brittle external OPA logic. In many organizations, infrastructure patterns are encapsulated into approved modules (e.g., networking, S3 buckets, IAM roles, etc.). When these patterns are modularized, developers can safely self-serve infrastructure by consuming those modules rather than building resources directly. Proposed solution Add first-class lifecycle state for each module version: active deprecated (optional sunset_date) unsupported Ideal behavior Using a deprecated version: plan succeeds but emits a warning stating it’s deprecated, recommended version, and sunset date (if set). Using an unsupported version: plan fails (hard stop). Acceptance criteria Registry UI shows lifecycle state per version and (if applicable) sunset date. Lifecycle state is persisted per version and queryable via GraphQL. Deprecated usage generates a warning surfaced in the run. Unsupported usage blocks the run automatically.

MCP tool for searching for runs

It looks like the current tools in the MCP server only allow either getting a specific run using a stack id and run id, or listing the runs in a stack. For some use cases it would be more efficient to have a tool that allows searching or filtering the runs. In particular so that an agent can find the proposed runs for a pull request based on the commit id

Slack Channel Terraform Resource

We’d like to be able to manage the integrated Slack channels and their scopes via a Terraform resource in the Spacelift provider

Provider Signature Verification on Upload

Add server-side GPG signature verification when providers are uploaded to Spacelift's registry. Currently, Spacelift accepts providers even if the signature file is corrupted. Validating the signature on upload would catch corruption regardless of whether it happened on the client side or in transit, preventing broken providers from ever being published.

External secrets and certificates from Key Vault

Today, we have stack specific secrets that live in Azure Key Vault. To use them in Spacelift, we end up duplicating them into a Spacelift context or stack environment variables, so we have to maintain the same value both in Key Vault and in Spacelift. That creates extra work, increases the chance of drift, and makes rotation harder. What I would like is a native way in Spacelift to reference an external secret store, starting with Azure Key Vault. For example, instead of pasting the value into a context, I want to be able to define something like “this variable comes from Key Vault secret X” and have Spacelift fetch it at runtime using the stack’s identity, service principal, or managed identity. This is similar to how Azure DevOps variable groups can pull from Key Vault, if the identity has access, the secret becomes available as a variable during the run.

Better support for adhoc ansible runs

As an infrastructure owner, I would like to be able to execute arbitrary ansible playbooks using an existing ansible stack. Spacelift currently locks each stack to a single playbook, which makes it difficult to make use of ansible’s full capabilities for managing the operating systems and applications on our EC2 infrastructure.

Notification Policies Access to Variables

We use stack contexts and environment variables to store useful metadata, such as the version being deployed. However, notification policies do not have access to those context variables. Because of this, we have to run custom scripts before the plan step to expose values as flags, just so notifications can read them. It would be much cleaner if notification policies had access to the same variables that plan policies do, including context-attached environment variables. This would remove the need for workarounds and simplify our notification logic.

Expose Full Dependency Tree and Root Run ID in Policies

We are heavily using stack dependencies, and when one stack triggers many others, we need visibility into the full dependency chain inside policies. Right now, we only have access to limited upstream information. It would be very helpful if every policy type, including notification policies, had access to the full dependency tree and the root run ID. This would allow us to: Track who originally started the run Thread Slack notifications properly Reference the same root run across all dependent stacks Build cleaner approval and notification logic Currently, we have to rely on workarounds and custom scripting. Having full dependency visibility in policies would simplify our setup significantly.

Allow MCP-based integrations with Spacelift without requiring spacectl

Problem Spacelift currently provides MCP functionality through the spacectl MCP server. To use MCP with Spacelift today, users must: Install spacectl Authenticate using spacectl profile login Configure their coding assistant to run: spacectl mcp server Requiring a CLI purely to support MCP integrations makes it harder to integrate Spacelift into internal platforms that standardize on API-driven MCP servers. Proposed Solution Provide a way to integrate Spacelift into MCP-based AI systems without requiring spacectl. This could be achieved in one of two ways: Option 1 Provide an official Spacelift MCP server that communicates directly with the Spacelift API / GraphQL. Option 2 Provide documented integration patterns that allow customers to easily build their own MCP servers using the existing GraphQL API. Ideal Capabilities An MCP integration should allow AI tools to interact with Spacelift capabilities such as: discovering modules in the Spacelift module registry retrieving module metadata (inputs, outputs, examples) identifying the latest module version generating infrastructure code using approved modules This enables AI assistants to generate infrastructure that aligns with an organization's approved module ecosystem. Customer Value Many organizations are adopting AI-assisted infrastructure development. When infrastructure patterns are encapsulated into approved modules, AI tools can safely generate infrastructure code by discovering and using those modules. Allowing MCP integrations without requiring a CLI dependency would make it easier for organizations to integrate Spacelift into internal developer platforms where multiple systems are connected through MCP servers and APIs.

Use two-way merge for PR run

When PR is open only last changeset is retrieved by spacelift. In case the target branch of PR has changed, these changes are not reflected in PR run. Results of the plan are not the same as results of the plan when the PR is merged.

Support dynamic VCS repository input in Templates

Templates currently resolve the VCS repository field at publish time, meaning the repository is baked into the template version and can't be provided as a dynamic input. This prevents using Templates for use cases where the same stack configuration needs to be deployed across multiple repositories - e.g. a "Stack Vendor" template that engineers deploy from to onboard their repo.

Allow cancelling in progress runs when notrigger is to true

When notrigger: true is set, Spacelift skips creating a new run entirely and since cancellation only happens as a side effect of a new run being created, the cancel list gets silently ignored.

Enable downloading of a stack's state changelog

An easy way to export stack state change logs for auditing. e.g., Something like an export of the State History?