ansible-sign VS community.hashi_vault

Call for contributors! You might have noticed that a lot of the docs in the ecosystem have started applying the Ansible Sphinx theme to documentation in recent weeks. Ansible Sign and Ansible Builder are just two such projects that have recently adopted the theme. And, as more teams start using it for their docs, we're identifying maintaince and improvements to make the Ansible Sphinx theme even better. Fork the sphinx-ansible-theme repository and lend us your expertise!

I am very excited to present my first blog post! Project signing is a new feature developed for Red Hat Ansible Automation Platform that came out in the latest 2.3 release. It enables users to sign project-based content (think playbooks, workflows, inventories, etc.) and verify whether or not that content has remained secure. It also features a new CLI tool, ansible-sign. This blog post will explain how it works, illustrate how to implement it, and highlight a few scenarios. Check it out 👉️ here.

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.