First off, cool drift detection approach!
I'm migrating away from our custom bash scripts to tfe-drift and was wondering how you deal with plan errors and retrying those.
We commonly ran into plan errors in the past due to the temporary unavailability of e.g. modules and introduced in our bash script a retry since it would otherwise trigger a false positive in our alerts.
I looked into tfe-drift but didn't find anything on that topic. E.g. if I was running in controller mode, the not-before would not rerun errored plans but just strictly filter anything out regardless of their status.
Using the GitHub Action I could deal with it myself but thought maybe tfe-drift already deals with it somehow.
First off, cool drift detection approach!
I'm migrating away from our custom bash scripts to
tfe-driftand was wondering how you deal with plan errors and retrying those.We commonly ran into
plan errorsin the past due to the temporary unavailability of e.g. modules and introduced in our bash script a retry since it would otherwise trigger a false positive in our alerts.I looked into
tfe-driftbut didn't find anything on that topic. E.g. if I was running in controller mode, thenot-beforewould not rerunerroredplans but just strictly filter anything out regardless of their status.Using the GitHub Action I could deal with it myself but thought maybe
tfe-driftalready deals with it somehow.