RB
I'm thinking if this is built into atlantis, it may overload this single thread machine, so im for the option to do drift detection as a helper outside of atlantis....
I don't know if I'd want it to create a pull request. Id rather it hit a webhook (e.g. mention the drift in slack with a link) with custom data....
Another way to set this up is similar to how atmos has set it up where it runs the plans across root dirs and creates open github issues when drift...
Thanks @BenoitLF. This would be nice to add to our troubleshooting page. We welcome PRs if you have the time
Perhaps this command needs to be running Atlantis on a new pr or in a pre workflow hook? ``` git config --global --add safe.directory '*' ``` https://stackoverflow.com/questions/72978485/git-submodule-update-failed-with-fatal-detected-dubious-ownership-in-repositor
@lattwood what i don't fully understand is why does automerge require all plans to succeed? If a single plan fails, it will show one of the plans as failed and...
Quick links - Logs https://app.renovatebot.com/dashboard#github/runatlantis/atlantis
@fazith27 what atlantis version are you using?
It seems like a gitlab specific issue. I'm unsure if they changed their API or if this is an edge case that no one accounted for. Seems like the API...
Try `atlantis plan --verbose` It would help to know how you folks have deployed the app. I use the latest version and can see the logs within my eks cluster.