Stacks sometimes do not have Drifted status, when they should

Stacks that have drift detected, do not always have Drifted status - for example, this schedule run detected 13 changes in resources (it was just a proposed run, without triggering tracked run in response to drift detected). Yet, I don’t see any Drifted: true stacks in the stacks browser. This seems to be a case for both stacks with vendor set to Ansible or Terragrunt

Please authenticate to join the conversation.

Upvoters
Status

πŸ—‘οΈ Archived

Board

πŸ“ Feedback

Tags

Drift Detection

Date

3 months ago

Subscribe to post

Get notified by email when there are changes.