amq VS cisco.ios

We are a new initiative called "Ansible Middleware", which utilizes the power of Ansible automation to orchestrate the installation, configuration, and management of Enterprise Middleware using several collections. It provides you with several benefits such as a smoother release process, the same level of comfort as cloud infrastructure, making your application a first-class citizen of the Ansible ecosystem, and also making your middleware products easy to use and easy to automate. Currently, we have collections of WildFly, Keycloak, Infinispan, JWS, Active MQ, Jcliff and we are rapidly growing.

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: