← Back to all posts

Successful Drift Resolution Runs on Stacks with State "NONE" Should Trigger a Tracked Run

When a stack is in a “NONE” state and a drift detection run occurs finding no drift, instead of not tracking the run, it should create a tracked run so the stack switches to the “FINISHED” state, its resources are uploaded, etc.

Workaround
-
Problem
Stacks can get deleted and recreated programmatically at our company. When that happens, the new stack is listed as a "NONE" state stack. I want drift detection to plan these stacks automatically and show them as "FINISHED" if they didn't have drift. This way people do not need to manually trigger these stacks every so often

Please authenticate to join the conversation.

Upvoters
Status

👀 In Review

Board

💡 Feature Requests

Tags

Stacks

Date

5 months ago

Subscribe to post

Get notified by email when there are changes.