cisco.ios VS ansible-lint

cisco.ios has been released with bugfixes and features (changelog).

cisco.ios 4.4.0

A few updates on what the Networking team is working on: * we are developing some content related to interfaces and ospf * we are working on extending the capabilities of nxos_bgp_global to support the creation of neighbour templates; earlier we could use the module to just apply one that is already created * we are planning to release a filter plugin (ace_popper) which acts on a set of acls facts gathered from a network appliance, and removes ace entries on the basis of some matching criteria

Depedencies on other collections (defined in galaxy.yml) are resolved and installed by ansible-galaxy - unless you're doing an offline installation, then you need to do this manually. Missing collection dependencies are notified about at the time of installation.

I read here https://github.com/ansible-collections/cisco.ios/issues/698 that it seems to be by decide to not be able to remove single vlan from a trunk (if i have understand it correct) so i guess you need to do something like this?

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)

Taking a look at the github requirements page:

Ansible-lint version 6.14.6 is here, started using ruff linter along with 10+ bugfixes in this release.

Ansible-Devtools team made a new release of Ansible-Lint version 6.14.2 with couple of exciting bugfixes.

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.

ansible-lint 6.14 was released, dropping support for py38 and including over 25 changes and bugfixes.

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.

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.

Check https://github.com/ansible/ansible-lint/discussions/2534 for details and comment there if you detect any regressions.

There is more context here: https://github.com/ansible/ansible-lint/issues/578

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

I use vanilla vim or nvim with checks from ansible-lint.