community.fortios
ansible.utils
community.fortios | ansible.utils | |
---|---|---|
1 | 7 | |
0 | 67 | |
- | - | |
10.0 | 7.9 | |
about 2 years ago | 8 days ago | |
Python | Python | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
community.fortios
-
The Bullhorn #83 (Ansible Newsletter)
It looks like the community.fortios collection is effectively unmaintained. According to the current community guidelines for collections, we consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: community.fortios for more information or to announce that you’re interested in taking over the maintenance of (a fork of) community.fortios.
ansible.utils
-
The Bullhorn #83 (Ansible Newsletter)
We're happy to announce the following networking collection updates: * ansible.utils 2.8.0 has been released with new features (changelog) * cisco.iosxr 4.0.3 has been released with bugfixes (changelog) * cisco.nxos 4.0.1 has been released with bugfixes (changelog) * junipernetworks.junos 4.1.0 has been released with new features (changelog)
-
The Bullhorn #50 (Ansible Newsletter)
The ipaddr filters are broken in ansible.netcommon 2.6.0 release as we have recently migrated ipaddr filters from ansible.netcommon to ansible.utils. We have released utils 2.5.2 and netcommon 2.6.1 which fixed these two issues (ansible.netcommon#375, ansible.utils#148). For the FQDN issue, the ansible-core team has already merged the fix. This fix will be available in the March 28th release, which means that users of non fqdn ipaddr filters can use the old netcommon collection version 2.5.1 as a workaround until the next ansible-core release (March 28th) by the core-team. For fqdn ipaddr filters, users can use the latest versions of any of ansible.netcommon (2.6.1) or ansible.utils (2.5.2).
-
The Bullhorn #44 (Ansible Newsletter - now weekly!)
We hope you'll enjoy part1 and part2, and take a look at the collection and source repo where we'd love to hear your suggestions on how to improve the collection.
-
Help with Ipaddr Syntax (IP not in subnet)?
Also handy for this and other IP related tests, the Ansible.utils collection https://github.com/ansible-collections/ansible.utils /u/CertifiedKnowNothing
-
Need a parser that will help me compare free space of member switches
See: https://www.ansible.com/blog/using-new-ansible-utilities-for-operational-state-management-and-remediation https://github.com/ansible-collections/ansible.utils/blob/main/plugins/sub_plugins/cli_parser/ttp_parser.py
-
regex_findall filter does not work as expected, need help
Also, I've not done it this way, but I believe this could be short-cut even further using: https://github.com/ansible-collections/ansible.utils/blob/main/plugins/sub_plugins/cli_parser/ttp_parser.py#L23-L28
What are some alternatives?
sva.sentinelone - This collection provides several unofficial ansible modules and roles to use with SentinelOne management consoles
ansible.netcommon - Ansible Network Collection for Common Code
awx - AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
community.postgresql - Manage PostgreSQL with Ansible
news-for-maintainers - Announcements of changes impacting collection contributors and maintainers
ansible-borgbase - Ansible modules for managing borgbase SSH keys and repositories
community-topics - Discussions for Ansible Meetings
overview - Collections overview, how to request a namespace
ansible-build-data - Holds generated but persistent results from building the ansible community package