in spacelift ui I want to be able to click on the icon showing the current run state (applying, ...) and it should take me to the current run view

Worker Pool Job Routing

When drift detection is enabled on a stack, you are forced to use your self-hosted worker pool.

Enable drift detection without admin permission

To enable drift detection it seems as of now it requires ADMIN permissions. With AAC could there be a role introduced for drift detection that would not require admin permissions to be set?

UI / UX Rain Feature: Year round Ambient Visual Effects (ex. our Holiday snow feature)

Requesting additional ambient visual effects (similar to the holiday snow animation) to be available beyond seasonal use, such as a soothing rain or nature-themed effect. The customer shared that the existing snow effect was unexpectedly calming during long-running deploys. Having a subtle, mesmerizing visual helped make waiting for several minutes feel more pleasant and less tedious. Proposed Idea Introduce optional, non-intrusive ambient UI effects (e.g., rain, nature themes) that could be enabled during long-running operations like deploys. These could be: Available year-round Optional / user-toggleable Designed to be subtle and non-distracting

Drift detection notifications per stack owner or team label

Ability to route drift notifications based on stack level metadata. For example, each stack could have a label or owner field that maps to a Slack channel, alias or user list. When drift is detected, the system would send a notification directly to the right team instead of relying on a single global webhook. This is especially important where many teams own their own stacks.

Filter resources by attributes in the resources view

Ability to filter resources by their attributes, not only by IaC resource name. For example, I want to list all S3 buckets with a specific encryption configuration, or all resources with or without a given parameter. The data is already there in the inventory but today I need to click each resource, open the JSON on the right, and search manually. A filter on key and value would already solve most of this.

Reverse lookup: find stack by cloud resource

Ability to start from a cloud resource identifier or name and quickly find which stack manages it. Example: given an IAM role or S3 bucket name from an event or CloudTrail, I want to search in the resources view and see which stack is responsible for that resource. This makes it much easier to investigate manual changes, alerts and incidents that originate from the cloud side.

Support Terragrunt run-all with Spacelift Native State Management

Spacelift integrates with Terragrunt, but when using Terragrunt’s run-all functionality, Terraform state cannot be managed by Spacelift’s native state management. This limits the effectiveness of the integration for teams using Terragrunt to orchestrate multi-module and dependency-driven deployments.

Explorer-like inventory of providers/modules (and versions) across Stacks

It would be really helpful if Spacelift had an Explorer-like inventory view (similar to Terraform Cloud → https://developer.hashicorp.com/terraform/cloud-docs/workspaces/explorer ) showing providers/modules and their versions across all stacks. This would make it easier to : understand how far behind the stacks are see how spread out the module versions are across stacks Nice-to-have additions: - filters by stack/space/environment - charts showing version distribution - export to CSV - click-through to affected stacks

Option on spacelift_run resource to continue even if target stack is disabled

The spacelift_run resource has an optional wait block that allows it to continue if the run is in a defined run state, and to continue if it did not reach any defined end state. I would like to configure the resource to also continue if a run cannot be triggered because the target stack is disabled.

Display Raw Terraform Output Only

Not sure if it’s a change that needs to happen in Spacectl or spacelift itself. Any spacectl command that outputs logs (ie spacectl stack deploy or spacectl stack logs ) displays the output of Spacelift and Terraform. It’d be useful if we could optionally abstract all spacelift specific logs and only show the raw Terraform Output only. And possibly maybe a final line stating full spacelift logs can be seen on spacelift and link the run URL.

RBAC for module delete-version

It’s currently not possible to delete a module version without the space_admin permission on the root space. I would like to see a permission like MODULE_DELETE_VERSION available in RBAC.

Action overlay cover up list item details

On pages like Stacks or a worker pool, selecting items brings up an action overlay showing the number of items selected and actions to perform. This overlay covers up the list items, making it really hard to see what’s being selected and deselected. For example, in the attached screenshot, I couldn’t tell which stacks items 30 and 31 were. When I clicked the X to see them, it dismissed my selections. I found both behaviours frustrating.

Sort or filter on Delta, Issues column

There is a filter for Needs approval, although it may still be nice to use column sorting on Issues to group stacks (within a given set of filters or view) that have and don’t have issues. I’m not aware of a filter for Delta, e.g. terraform stacks that’ll add resources, or that’ll destroy them. It’d likewise be nice to group by or filter this way

Support outputs from multiple stacks to the same input in a downstream stack

I’d like to be able to configure multiple outputs to share an input in a downstream stack. For example. Stack A - Output: ecr_role Stack B - Output: codecommit_role… Stack X - Inputs: [ecr_role, codecommit_role] → allowed_roles

More Controls for PR Promotion

Would it be possible to require a PR Promotion run to be a minimum # of days old from mainline? Basically, we want to avoid a case where a user makes a PR, leaves it for X days and then decides to promote it for testing without realizing its out of date. This is mainly for risk reduction, not total avoidance of issues with shared state terraform states.

Stacks UI

At the top of the Stacks UI it has a few tabs All, Needs attention, Failed, On Hold, In progress, Finished. There is no indication that a stack is in one of those states unless i click on that tab or filter by the state on the left side. Would be handy to see the number of stacks that are in each state similar to terraform cloud.

How to get rid of LaunchPad?

How do I get rid of the LaunchPad? It seems rather useless after onboarding. I keep hitting it thinking I’ll see the Dashboard. I’d much prefer having the Dashboard in its place.

Difficult to select a single stack on stacks page

I don’t like the behaviour on the stacks page where when I select a stack, it selects all the stacks above it. I then have to deselect all the stacks above it to get the one I want. The checkboxes beside each stack should just select that stack, not that stack and everything before it.

Blueprint GUI to Stacks created from Blueprints

Have a blueprint style form for stacks so that non-terraform friendly users can update their stack with updated variables (I.E. Azure App Service Plan type). Currently the users will have to change the TF vars but that’s not an elegant solution. Also force an option to LINK the blueprint template with the stack. So if you update the blueprint, it updates the linked stacks.