Skip to main content

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

Workaround
Status: 🔭 Discovery2 comments

This request was merged into another request

Comments2

  • Black Breeze

    •

    Jan 29

    Thanks for taking the time to raise this @Colin Payne-Rogers . I see where you’re coming from, I’m just trying to conceptualize the solution.

    See, the problem is that unlike “needs approval“ which is a simple boolean, delta is a complex metric that includes deletes, updates, creates etc. What should we sort by? The sum of all changes? Allow sorting by each change type?

    In order to design the experience, we would like to first understand what scenarios you envision yourself using this new hypothetical mechanism for. Can you please share a bit more about your workflow?

    • Jade Clay

      •

      Jan 30

      Thanks for your response @Marcin Wyszynski, there are two ways that I could see delta sorting working that would improve my experience:

      • Treating it like a boolean to surface or hide stacks with a delta (but don’t otherwise change the order before applying this sort)

        • This can be done with the current interface, e.g. by filtering for unconfirmed stacks, or with a more complex state filter to hide unconfirmed stacks)

      • Sorting within the delta categories using the same precedence that you use when displaying a delta from left to right (add > change > delete > move, iirc)

        • This can’t be done currently afaik

      In terms of my workflow, I’m looking to sort or filter within unconfirmed stacks for one of the following:

      1. A set of stacks that have a particular delta (e.g., let’s say I have 150 stacks that all use the same module, and I add a null resource to that module as an input check, then trigger those stacks and want to find stacks that just have a +1 for that new resources, so I can review or apply those, but leave stacks with a more complex delta to be reviewed by a domain expert on that stack)

      2. Any stack that has a delta that looks safe to apply (e.g., out of the almost 1,000 stacks we have so far, I might want to manually review stacks in an unconfirmed state with only additive and/or changing deltas to see if they can be run, are a new-to-me type of drift)

      Neither of these cases is horrible to handle with the current interface, e.g. by scrolling through all unconfirmed stacks, but anticipating the number of stacks to grow drastically, it would be nice to have.