community.network VS community.hashi_vault

Updates from Ansible networking team. * We have enabled periodic jobs through GHA for network collections. * We are working on community.ioscm collection which works for iosxe on controller mode, when the appliance is in sd-wan infrastructure! * IRC Meeting changes. * We want someone who will look into ansible-lint fixes for community.network collection.

The community.network collection versions 3.3.1 (Final EOL release, changelog) and 4.0.2 (changelog) have been released!

community.network collection 5.0.0 has been released! See the changelog for details. Special thanks to felixfontein for removing flat-mapping and other improvements!

Community Network Collection 4.0.0 has been released and is available to download! See changelog for details regarding the major changes and deprecated features!🎉

The community.network minor releases 2.3.0 & 3.3.0 have been released!🎉 Thanks to all the awesome people who contributed to them!❤️

community.network 1.3.7 & 2.2.2 & 3.2.0 have been released with some improvements and bug fixes (see changelogs 1.3.7, 2.2.2, 3.2.0 for more details)🎉

community.network collection versions 1.3.6, 2.2.1, and 3.1.0 have been released! Special thanks to felixfontein!

We are looking at reducing the maintenance for old stable branches for community.general and community.network collection repositories. We'd welcome your feedback, in particular if you think you may be negatively impacted by the change. Full details of the proposal, and the ability to record your vote can be done via community-topic#55.

My way of doing private SSL (not necessarily the easiest):

* own CA, to be distributed to all systems via Ansible playbook or Dockerfile directives

* Hashicorp Vault with enabled PKI engine

* Ansible Hashivault module [1]

* Ansible role & playbook to tie it all together

* CI enviroment for automated deployment of SSL certs to target systems

Works flawlessly once set up, including restart/reload of affected services. Might do a writeup on my personal blog at some point.

[1] https://github.com/ansible-collections/community.hashi_vault

community.hashi_vault 5.0.0 has been released. See the collection changelog for details.

community.hashi_vault version 4.2.1 has been released with updated documentation for the vault_kv2_write module. There are no functional changes.

community.hashi_vault version 4.2.0 [changelog] has been released with a new KVv2 write module and a warning/deprecation for duplicated term string option use in the hashi_vault lookup.

The community.hashi_vault collection has released version 4.1.0 with a new vault_list module and lookup from a new contributor! There are also some upcoming deprecation announcements for hvac and ansible-core support.

community.hashi_vault version 4.0.0 has been released, with previously announced breaking changes to some default values, and improvements to module documentation with attributes that describe the use of action groups and check mode support.

community.hashi_vault version 3.2.0 has been released with support for the azure auth method, thanks to new contributor @jchenship. This release also includes retries on HTTP 412 and a bugfix affecting requests>=2.28.0.

community.hashi_vault has released version 3.1.0, announcing a change to a default value that will take place in 4.0.0.

The community.hashi_vault collection is looking for feedback about support for end-of-life Python versions going forward. Join the discussion.

community.hashi_vault version 3.0.0 has been released, dropping support for Ansible 2.9 and ansible-base 2.10, as well as removing some deprecated features.