angystardust

@l0renzor I might be wrong but I think that the development of the fortios modules has been moved here: https://github.com/fortinet-ansible-dev/ansible-galaxy-fortios-collection

@cerih thanks a lot for the tip! But what "Mirror on Sync" option is intended for? What feature I lost if i disable this option?

An interesting article about "split DNS" has been published on Fedora magazine: https://fedoramagazine.org/systemd-resolved-introduction-to-split-dns/

Wow...i didn't know about all that different input formats. It reminds me the syntax of the `date` command. By the way I think that we should support the AAAA-MM-GG format...

@lqueryvg now that extras repo is definitely closed, you should make a PR to the main ansible repo. I think many people need your module so having it by default...

As mentioned by the foreman devs here (https://groups.google.com/d/topic/foreman-dev/n1QkZF1QVxU/discussion), I'm afraid that the "runcmd" support on Linux is limited by the vmware CustomSpecs...

as AWX/Tower doesn't support boolean in surveys yet, do I need to convert my variable to a string and evaluate for a matching string, right?

Thanks @wenottingham. Anyway, if I filter the extra-variable passed by the awx survery with the bool filter, my playbook should be able to evaluate it correctly, isn't it? :thinking:

Since Fedora33 went GA, we now have `systemd-resolved` enabled by default so we need to find a proper way to manage this DNS mess in a sane way. Actually, one...

@peterhoeg on fedora you can also inject them using `resolvconf -a ppp0 < ~/you-own-personal-resolv.conf`so passing the parameters defined in a custom resolv.conf