<https://www.taccoform.com/posts/tfg_p3/>
# github-actions
e
cc @Matt Calhoun
r
@PePe Amengual
p
yes, I gave it a read
I think is a very simplistic “good enough” solution with no feedback loops except for some task status etc
in my opinion Drift detection should have an option to have more detail and historical reference of what happened etc
so in a GitOps scenario you should be able to see what happened and hopefully that is recorded in the repo too
j
yeah, I kinda kept it open ended with the alerting mechanism on this article. Slack, email, etc. For something more in-depth, I would use a dedicated tool, but I think for a lot of people, this and possibly cloudtrail should be a good start. Also having strict rules on how terraform code is promoted through environments should help eliminate drift
p
totally, your article is pretty good , and for most people this is more than enough for sure
🙏🏽 1
Where I come from if from the Atlantis side ( I’m a Maintainer) and I just implemented a github action workflow similar to what you propose in the article but for a tool that already does GitOps the github action user workflow is not the best to go about it and makes unnecessary steps to be needed for implementation
Ideally the GitOps tool ( Atlantis, spacelift, TFC) should communicate back through more than one channel
💯 1
and in case of finding drift it should report back in or leave a trail of what it did if autoremediation was done, in form of a ticket, PR or whatever
and hopefully the GitOps tools can have and
/api/drift
than can be trigger by a simple workflow(not github specific) or support multiple VCSs too
j
yeah, I guess hoping what's committed to
main
is the desired state and if the drift is too destructive, then maybe triggering an escalation for human review
p
correct