ansible-pfsense
ansible-pfsense copied to clipboard
opoplawski
Retire this repo
We should retire this repo in favor of the pfsensible.core collection. However, I still need to migrate to using the collection at work. But I hope to get to that in a couple weeks.
@f-bor anything hold you back from using the collection?
Anyone else?
Same as you: I need to migrate all the playbooks we have (and to update our old ansible setup).
I need to build modules for at least unbound and squid (+ squidguard). I will do this using the collection repo. Should I also change my existing pull request or do you want to merge it here?
@coffeelover until we retire this repo, all new PRs should be filed against ansible-pfsense. Changes flow out from there.
I'm a heavy user of mitogen, and unfortunately I'm running into https://github.com/mitogen-hq/mitogen/issues/820 If that doesn't get fixed soon I guess I'll bite the bullet and switch to FQCNs, but I'm hoping to avoid that for now.
Something to not forget is that this repo still has wiki pages filled with info where the pfsensible/core repo only shows Welcome to the pfsensible/core wiki!.
EDIT: not sure if the GitHub wiki should be used again for that info, since contributors who want to help improve the docs can't submit pull requests for the wiki (I spotted a simple mistake in one of the wikis). But that probably is another discussion.
EDIT2: the reason why the Welcome to pfsensible/core wiki! message is shown is because the links in the README are broken. The info actually is there already (a pull request exists for fixing the links: https://github.com/pfsensible/core/pull/25). This comment can be ignored.
ansible 2.9 is EOL, EL8.6 has moved to ansible-core 2.12, so I am finally making the switch to pfsensible/core and will be dropping support for this repo soon. Given the constraints on my time this will probably drag out a bit and not be as clean as I would like, but the time has come.