ansible-lint
ansible.netcommon
Our great sponsors
ansible-lint | ansible.netcommon | |
---|---|---|
10 | 6 | |
2,713 | 134 | |
- | 3.0% | |
9.4 | 7.8 | |
about 2 years ago | 6 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-lint
-
The Bullhorn #99 (Ansible Newsletter)
Ansible-lint version 6.14.6 is here, started using ruff linter along with 10+ bugfixes in this release.
-
The Bullhorn #95 (Ansible Newsletter)
Ansible-Devtools team made a new release of Ansible-Lint version 6.14.2 with couple of exciting bugfixes.
-
The Bullhorn #94 (Ansible Newsletter)
The Devtools team has released ansible-lint version 6.14.0, which includes 23 bugfixes and 3 minor changes. Please refer to the changelog here for more information.
-
The Bullhorn #93 (Ansible Newsletter)
ansible-lint 6.14 was released, dropping support for py38 and including over 25 changes and bugfixes.
-
The Bullhorn #92 (Ansible Newsletter)
Ansible-lint 6.13 introduces a new feature that allows users to utilize a .ansible-lint-ignore file. This file contains skip-rules that are loaded from the ignore file which is adjacent to the config file. Additionally, users can take advantage of the --generate-ignore argument to dump any current violations into an ignore file.
-
Open Source Collection of Ansible Good and Bad Practices
Cool, but ansible-lint and the official RedHat docs are a much better way to ensure you're using the official best practices. No offense, but stuff two random guys on Reddit threw together isn't a great resource for best practices.
-
ansible-lint 6.8.0b1 is out
Check https://github.com/ansible/ansible-lint/discussions/2534 for details and comment there if you detect any regressions.
-
Correct use of block: and when: (key-order)
There is more context here: https://github.com/ansible/ansible-lint/issues/578
-
The Bullhorn #69 (Ansible Newsletter)
ansible-lint 6.4.0 was released with lots of bugfixes and a new feature called "profiles", one that allow you to easily pick which set of rules you want to follow. https://github.com/ansible/ansible-lint/discussions/2254
-
What is your preferred software to write playbooks?
I use vanilla vim or nvim with checks from ansible-lint.
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
What are some alternatives?
ansible-vim - A vim plugin for syntax highlighting Ansible's common filetypes
ansible.utils - A collection of ansible utilities for the content creator.
ansible-language-server - 🚧 Ansible Language Server codebase is now included in vscode-ansible repository
ansible-meraki - Cisco Meraki Ansible Collection
ansible.scm - An ansible collection for prescriptive retrieval and publish using git
creator-ee - Ansible Execution environment targeted for content creators. It includes most development tools such ansible-lint, molecule, ...
community.zabbix - Zabbix Ansible modules
Pure1-Collection - Ansible Collection for Pure Storage Pure1
coc-ansible - ansible-language-server extension for coc.nvim
community-topics - Discussions for Ansible Meetings
conventional-pre-commit - A pre-commit hook that checks commit messages for Conventional Commits formatting
community.aws - Ansible Collection for Community AWS