Currently, the filters don’t allow you to sort by delta. I think this could be as simple as sorting as the sum of all changes, or potentially giving more weight to updates/deletes.
Hey, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.
Black Breeze
•
May 8, 2025
Thanks for the suggestion! Sorting by delta definitely sounds useful—especially in setups like yours where multiple environments are managed centrally and you want to quickly spot which ones need attention.
We’d love to dig in a bit deeper to make sure we’re solving the right problem in the best way. A couple of things we’re curious about:
When you say “delta,” is it about the total volume of changes, or more about their impact (e.g. deletes > updates)?
Are you typically using this to react to drift, or to proactively scan for infra that’s out of sync?
What would a “great” experience look like here—for example, is the goal to open Spacelift and immediately know where to focus?
Understanding that context will help us figure out if this is just a sort toggle—or something bigger, like drift triage, remediation planning, or infra health visibility.
Really appreciate you sharing this—we’re listening.
Indigo Stew
•
Jun 16, 2025
@Marcin Wyszynski
When you say “delta,” is it about the total volume of changes, or more about their impact (e.g. deletes > updates)?
this is a good question. In my opinion the “impact” is more important, but quantity could be useful as well. I think it would be useful to have a “blast radius” score similar to what is suggested in the plan policy, in addition to being able to sort by absolute quantity of changes
Are you typically using this to react to drift, or to proactively scan for infra that’s out of sync?
not reacting to drift, though it would be useful for this. We deploy components across many accounts with separate stacks (one per component/account), and it would make approving changes more simple if we could understand the outliers.
What would a “great” experience look like here—for example, is the goal to open Spacelift and immediately know where to focus?
an additional column for blast radius and quantity of resources affected would be ideal
This request was merged into another request
Comments3
Natalia Gazda
Jul 16
Hey, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.
Black Breeze
May 8, 2025
Thanks for the suggestion! Sorting by delta definitely sounds useful—especially in setups like yours where multiple environments are managed centrally and you want to quickly spot which ones need attention.
We’d love to dig in a bit deeper to make sure we’re solving the right problem in the best way. A couple of things we’re curious about:
When you say “delta,” is it about the total volume of changes, or more about their impact (e.g. deletes > updates)?
Are you typically using this to react to drift, or to proactively scan for infra that’s out of sync?
What would a “great” experience look like here—for example, is the goal to open Spacelift and immediately know where to focus?
Understanding that context will help us figure out if this is just a sort toggle—or something bigger, like drift triage, remediation planning, or infra health visibility.
Really appreciate you sharing this—we’re listening.
Indigo Stew
Jun 16, 2025
@Marcin Wyszynski
When you say “delta,” is it about the total volume of changes, or more about their impact (e.g. deletes > updates)?
this is a good question. In my opinion the “impact” is more important, but quantity could be useful as well. I think it would be useful to have a “blast radius” score similar to what is suggested in the plan policy, in addition to being able to sort by absolute quantity of changes
Are you typically using this to react to drift, or to proactively scan for infra that’s out of sync?
not reacting to drift, though it would be useful for this. We deploy components across many accounts with separate stacks (one per component/account), and it would make approving changes more simple if we could understand the outliers.
What would a “great” experience look like here—for example, is the goal to open Spacelift and immediately know where to focus?
an additional column for blast radius and quantity of resources affected would be ideal