community-topics VS community.hashi_vault

There is a community vote on a new policy for community.general on which ansible-core versions will be supported in new major releases. Basically support for ansible-core versions will be dropped if they were EOL at least a few weeks before the major release. For the upcoming community.general 8.0.0, that means that it will drop support for ansible-core 2.11 and 2.12 and require at least ansible-core 2.13. Details can be found in the associated issue.

As mentioned in The Bullhorn #113, we've opened a community / steering committee vote on declaring ngine_io.exoscale an effectively unmaintained collection and remove it from the Ansible 10 community package. Since then, there has been a new release. As a result, the vote ended with the decision to keep the collection in the community package.

2023-07-12: Community WG meeting, 18:00 UTC (propose topics here)

Hi everyone. We're working on making Ansible community documentation a separate project to ansible/ansible. The purpose is to benefit the Ansible community by decoupling community doc initiatives from core release cycles. This change also removes the Ansible Core team as the gate for other doc related efforts that will meet community needs, such as putting source content for docs.ansible.com under the direct control of the Steering Committee. Overall this change is a first step towards providing greater access and ownership of docs.ansible.com to the Ansible community.

Looking for your feedback on making community docs a separate github project to ansible/ansible, starting with moving /docs from ansible/ansible to ansible/ansible-documentation. See this issue for details.

It looks like the netapp.elementsw collection is effectively unmaintained. According to the current community guidelines for collections, we consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: netapp.elementsw for more information or to announce that you're interested in taking over the maintenance of (a fork of) netapp.elementsw.

The netapp.aws collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works.

As mentioned in The Bullhorn #98, we consider netapp.aws an effectively unmaintained collection. Therefore, we've opened a community / steering committee vote on removing it from the Ansible 10 community package.

2023-05-10: Community WG meeting, 18:00 UTC (propose topics here)

Work continues combining several pytest plugins for ansible.

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.