Hi!
I've noticed that the drift detection in tf-controller, in fact, only detects changes, and even though it outputs/logs terraform code to showcase those changes, it does not generate any plan or hash to apply those changes manually. What makes me think this is a bug is the fact that, when auto approval is on, the drift changes are automatically applied, so it is supposed to help "correct" the drift.
Maybe I'm doing something wrong, but I think it would be a nice addition to generate a new plan when detecting drift, storing it in the secret and asking for a new commit with the hash, instead of having to run tfctl replan (resource) to force that.
Thank you in advance :)
Hi!
I've noticed that the drift detection in tf-controller, in fact, only detects changes, and even though it outputs/logs terraform code to showcase those changes, it does not generate any plan or hash to apply those changes manually. What makes me think this is a bug is the fact that, when auto approval is on, the drift changes are automatically applied, so it is supposed to help "correct" the drift.
Maybe I'm doing something wrong, but I think it would be a nice addition to generate a new plan when detecting drift, storing it in the secret and asking for a new commit with the hash, instead of having to run tfctl replan (resource) to force that.
Thank you in advance :)