Add a visual batch in the stack UI for forced-apply.
When creating a run, now we have the option to force apply that single stack or in cascade.
The issue surfaces when the run is queued or ready, because we cannot know that that option was enabled.
It is only shown after the plan phase, because it shows the apply phase with the force applied.
I think it would be very useful and interesting to have the ability to see that somewhere in the stack of runs and also in each individual run. Together with this, I think that should be added to the GraphQL API for when listing the runs for the workers queue, and add the filter in the workers queue UI.
- Workaround
- None
- Problem
Log in to comment and vote
Comments1
Natalia Gazda
Apr 17
Hey @Julio Chana Thanks for the detailed feedback about force apply visibility. I understand how seeing this information earlier in the run lifecycle would help with your operational workflows.
Currently, you can identify force apply runs once they reach the plan phase, where this information becomes visible in the run details. For immediate operational needs, you might consider:
1. Using notification policies to alert on run state changes, which can help you monitor critical runs as they progress
2. Leveraging the audit trail to track force apply usage patterns across your organization
3. Setting up monitoring on your worker pools to observe queue patterns and resource utilization
While we see how this would streamline your specific workflow, we're currently focused on features that unlock entirely new use cases for our broader user base. I've noted your feedback for future consideration as we continue to enhance our operational visibility features :)