Having Ansible just push out changes as soon as they're merged to `main` (or whatever) is pleasantly CI/CD like, and means that you can solicit pull requests from interested parties who may not have privs to run Ansible, and not have to push out their changes by hand once the PRs are merged. But, it makes it harder to make temporary changes outside of Ansible, which maybe you want a hard and fast rule against, but which is often pretty useful for testing things, especially on sandbox type hosts.
Having Ansible run some playbook(s) (out of cron, or the scheduler of your choice) periodically and report back on any drift is another way around the "how do you test things" problem, but it means that you have to then take some additional action to push out desirable changes. But it can be simpler than coming up with a way to say "temporarily don't let Ansible smite my changes on this host, I'm testing stuff". On Tuesday, June 27, 2023 at 3:11:44 PM UTC-4 John Petro wrote: > Good Afternoon, > I was wondering what you all are doing to manage configuration drift. > Are you having ansible fix the drift, are you having it notify you of the > drift, or are you doing something else. At work, we are preparing to start > having some conversations about what we want to do, and I thought this > information from you all might be helpful in our journey. > > Thanks for your time!! > > ---john > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/eac989eb-70d2-4c8e-865a-03ba78c50e2an%40googlegroups.com.
