Move the "Mark for Deletion" button

The “Mark for Deletion” in “Organization Settings” is awfully close to other buttons in the menu. It seems very dangerous to have this option so close to other buttons without confirmation if clicked. I’d suggest moving this button so mewhere else and adding a confirmation after clicking

Add Azure AD group name to spacelift IDP Group Mapping since it only accepts ID

support rego.v1

Support rego.v1 for policies

spacectl local-apply

To make our TF code work with Spacelift, we had to add assume_role_with_web_identity block with role_arn and web_identity_token_file into our providers definition as per the documentation. I have seen that spacectl has feature called "local-preview", where you can run terraform plan with your local code. I find that very useful. However, would it be possible to also run terraform apply in a similar way? I find this handy for early stage / crude development because I have witnessed many Terraform deployments to pass terraform plan, only to fail on terraform apply.

Workers hard limit on account level or space level

Is it possible optionally to turn on workers limit on account or space level? Purpose of request is to avoid accidentally having too many workers running.

Multi Stack Orchestration

We would like to deploy multiple stacks in tandem, together as a single unit. The use case for this would be to deploy multiple services to an environment, or to create an entire environment on demand at the click of a button.

Expose the same metrics as Datadog via prometheus

It would be really nice to get metrics on # runs, run success, # stacks, etc. via Prometheus so we can create custom internal dashboards with this info. It’s helpful for measuring adoption, but we don’t use Datadog so we can’t get the info from there.

New integration request from the website: It would be nice to see Atmos as an integration here

Michael Rosenfeld requested a new integration from the website: It would be nice to see Atmos as an integration here

Retry proposed runs

For the same reason you want to retry tracked runs, also a proposed run should be able to be triggered in case of certain failures. Currently only tracked runs are checked

Expose attached cloud integration or AWS(/GCP/Azure) identifier to policies

It would be great for policies to know where specific resources are being deployed. For example: what cloud integration is attached to the stack what aws account id / role is attached to the aws providers (and similar for GCP / Azure) This information can be very useful if actions need to be taken on specific AWS accounts / GCP projects, etc …

Resizeable log textboxes

Although we can fully expand a log textboxes to full screen, sometimes I’d rather just slightly resize to be taller, particularly when I’m on a vertical-oriented monitor with lots of real estate to work with.

Differentiate boxes in Resources view

Currently all resources shown in the Resources view are displayed as generic grey boxes (unless they have drift). It would be nice if the Spacelift-specific resources (e.g., stacks, modules, contexts, context files, etc.) each showed up with a unique color and/or icon to differentiate them from each other. This would enable the Resources view to paint a more comprehensive view of one’s infrastructure. Additionally, it would be nice if the “parent” view, or some new, view grouped the resources by the Space in which they reside. The current parent grouping appears to do so by account, which is not all that useful unless one has multiple accounts.

Enable Sampling for the Administrative User

Observed Behavior: If logging in as an Administrator, even though the login policy is configured to set sampling := true, the login is not captured. Why this would be valuable: As an Administrator, I would like to configure the login policy ahead of involving other team members/users. The sample would have showed me what teams are being sent over, which would allow me to write a more comprehensive and security login policy.

Option to auto attach integrations to stacks using labels

For example, the integration can include an auto-label feature that attaches stacks with specific labels. This is very useful for managing integrations across numerous stacks created using various methods or originating from different parts of the code.

Consistent usage of timestamps everywhere

When viewing some pages, like the Stacks, a timestamp is shown in a human-friendly way as “X days ago“, with an exact date/time as the tooltip. When viewing other pages, like the Stack Run History, a timestamp is shown as an exact date/time, with “X days ago” as the tooltip. All pages that show a timestamp should be looked at for consistency. If such a wholistic change is going to take place, the behavior should be changed, as well: Ideally, “recent” timestamps would show the human-friendly way, with a reversion to date/time once they are no longer “recent”. This “default” behavior should be configurable on the user settings page, such that users can pick “human recent”, “human always”, and “time stamp always”, as well as set the “recent” window. As an additional implementation note: When showing human-friendly timestamps, it’s important that they update, as the page continues to be shown. It would be less than ideal to show that something was done 1 minute ago on a page that has now been loaded for an hour.

Add ability to automatically attach contexts to stacks in owning or inherited spaces

Allow complex variables in context

I have a need to create a variable in a context that needs to be in json format and be kept a secret so it doesn’t need to be stored in source control

Add support to remove tags from metrics being sent to datadog

The terraform-spacelift-datadog module has common tags that are included on every metric https://github.com/spacelift-io/terraform-spacelift-datadog?tab=readme-ov-file#common-tags There is also support for adding extra_tags. What is not possible is to exclude the common_tags. The idea here it to add a new input such as exclude_tags which would allow a user to reduce the amount of tags being added to the metrics. Example usage: exclude_tags = ["run_note", "run_url"] Ideally, the tags on the metrics would then be extra_tags + common_tags - exclude_tags

Support opentofu/terraform built-in testing framework

Opentofu and Terraform both have testing frameworks. I realize Terraform will be hard to support given the license changes but adding it for the sake of completeness.

Automatic PR Generation with Blueprints

Requesting Blueprints to have the ability to automatically generate Pull Requests in Github from templates, similar to Backstage Software Templates. The auto PR generation would allow our users to follow the existing PR workflow for IaC (Terraform, Helm, K8s manifests). The intended workflow is similar to how Blueprints currently work, where users input values into a form, but instead of a stack being generated, Blueprints would automatically generate a pull request to the Git repository specified in the template, allowing users to add resources to existing stacks.