ansible.netcommon
ansible.utils
ansible.netcommon | ansible.utils | |
---|---|---|
6 | 7 | |
134 | 66 | |
0.0% | - | |
7.8 | 7.9 | |
5 days ago | 19 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.
ansible.netcommon
-
The Bullhorn #108 (Ansible Newsletter)
ansible.netcommon has been released with bugfixes (changelog).
-
The Bullhorn #93 (Ansible Newsletter)
ansible.netcommon 5.0.0
-
After endless hours of debugging ansible-pylibssh was the problem, (Tasks takes a long time on cisco ios)
Would you share the version of netcommon/ ansible-core version installed for you? and please file an issue here, https://github.com/ansible-collections/ansible.netcommon/issues. Regards
-
The Bullhorn #69 (Ansible Newsletter)
There have been a few networking releases this week: * ansible.netcommon 3.1.0 has been released with new features (changelog) * cisco.ios 3.3.0 has been released with new features (changelog) * cisco.iosxr 3.3.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).
-
Troubleshooting Net Put
This also affected net_get. New pull request to address this: https://github.com/ansible-collections/ansible.netcommon/pull/199
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?
ansible-meraki - Cisco Meraki Ansible Collection
community.postgresql - Manage PostgreSQL with Ansible
creator-ee - Ansible Execution environment targeted for content creators. It includes most development tools such ansible-lint, molecule, ...
community.fortios
Pure1-Collection - Ansible Collection for Pure Storage Pure1
ansible-borgbase - Ansible modules for managing borgbase SSH keys and repositories
community.aws - Ansible Collection for Community AWS
sva.sentinelone - This collection provides several unofficial ansible modules and roles to use with SentinelOne management consoles
community-topics - Discussions for Ansible Meetings
cisco.nxos - Ansible Network Collection for Cisco NXOS
ansible-build-data - Holds generated but persistent results from building the ansible community package