Browsing the latest collection documentation will show docs for the latest version released in the Ansible package not the latest version of the collection released on Galaxy.
Browsing the devel collection documentation shows docs for the latest version released on Galaxy.
We also separately publish latest commit collection documentation which shows docs for the latest commit in the main branch.
If you use the Ansible package and don't update collections independently, use latest, if you install or update this collection directly from Galaxy, use devel. If you are looking to contribute, use latest commit.
Please refer to the ansible-core support matrix to see which versions of ansible-core are still supported or end-of-life.
Generally, we release a new major version of this collection a little before the release of a new ansible-core version, which is around every 6 months. In that release, we will update the CI matrix to drop the core versions that are about to go EoL, and add in new core versions if they have not been added already.
We also regularly test against the devel branch (latest development commit).
See the CI configuration for the most accurate testing information.
We currently test against the latest patch version within the latest two minor versions of the latest major version of Vault. Put another way, we test against version Z.{Z|Y}.Z. For example as of this writing, Vault is on major version 1, with the latest two minors being 8 and 7. So we'll test Vault 1.8.Z and 1.7.Z where Z is the latest patch within those versions.
We do not test against any versions of Vault with major version 0 or against pre-release/release candidate (RC) versions.
If/when a new major version of Vault is released, we'll revisit which and how many versions to test against.
The decision of which version(s) of Vault to test against is still somewhat in flux, as we try to balance wide testing with CI execution time and resources.
See the CI configuration for the most accurate testing information.
Python 2.6, 2.7, and 3.5 are not supported in version 2.0.0 or later of the collection.
Currently we support and test against Python versions:
- 3.6
- 3.7
- 3.8
- 3.9
- 3.10
- 3.11
- 3.12
Note that for controller-side plugins, only the Python versions supported by the Ansible controller are supported (for example, you cannot use Python 3.7 with Ansible core 2.12).
The hvac Python library is required for this collection. For full requirements and details, see the collection's User Guide.
See the list of included content in the docsite.
See Ansible Using collections for more details.
See the contributor guide in the devel collection documentation.
Follow the instructions for releasing small collections in the Ansible community wiki.
Once the new collection is published and the Zuul job is finished, add a release in GitHub by manually running the GitHub Release workflow. You'll need to enter the version number, which should exactly match the tag used to release the collection.
See the rendered changelog or the raw generated changelog.
A: This was considered when the hashi_vault plugin was first moved from community.general to this collection. There are several reasons behind this:
- The other known HashiCorp content at that time (covering Consul, Nomad, Terraform, etc.) does not share implementation or testing with Vault content.
- The maintainers are also different. This being a community supported collection means separate maintainers are more likely to focus on goals that make sense for their particular plugins and user base.
- The HashiCorp products serve different goals, and even when used together, they have their own APIs and interfaces that don't really have anything in common from the point of view of the Ansible codebase as a consumer.
- It would complicate testing. One of the primary goals of moving to a new collection was the ability to increase the scope of Vault-focused testing without having to balance the impact to unrelated components.
- It makes for a smaller package for consumers, that can hopefully release more quickly.
Q: Why is the collection named community.hashi_vault instead of community.vault or community.hashicorp_vault or hashicorp.vault or any number of other names?
A: This too was considered during formation. In the end, hashi_vault is a compromise of various concerns.
hashicorp.vaultlooks great, but implies the collection is supported by HashiCorp (which it is not). That doesn't follow the convention of denoting community supported namespaces withcommunity.community.vaultlooks great at first, but "Vault" is a very general and overloaded term, and in Ansible the first "Vault" one thinks of is Ansible Vault. So in the naming, and even in the future of this collection and its content, we have to be mindful of avoiding and removing ambiguities between these products (and other Vaults out there).community.hashicorp_vaultis descriptive and unambiguous but is unfortunately quite long.community.hashicorpwould be good for a collection that aims to contain community-supported content related to all HashiCorp products, but this collection is only focused on Vault (see above question).community.hashicorp.vault(or any other 3-component name): not supported (also long).community.hashi_vaultisn't perfect, but has an established convention in the existing plugin name and isn't as long ashashicorp_vault.
- Ansible Collection overview
- Ansible User guide
- Ansible Developer guide
- Ansible Collections Checklist
- Ansible Community code of conduct
- The Bullhorn (the Ansible Contributor newsletter)
- Changes impacting Contributors
GNU General Public License v3.0 or later.
See LICENSE to see the full text.
Parts of the collection are licensed under the BSD-2-Clause license.