chore(deps): update dependency community.hashi_vault to v5 - autoclosed

This MR contains the following updates:

Package	Type	Update	Change
community.hashi_vault	galaxy-collection	major	3.1.0 -> 5.0.0

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Release Notes

ansible-collections/community.hashi_vault

v5.0.0

Compare Source

======

Release Summary

This version makes some relatively minor but technically breaking changes. Support for ansible-core versions 2.11 and 2.12 have been dropped, and there is now a minimum supported version of hvac which will be updated over time. A warning in the hashi_vault lookup on duplicate option specifications in the term string has been changed to a fatal error.

Breaking Changes / Porting Guide

• Support for ansible-core 2.11 and 2.12 has been removed (https://github.com/ansible-collections/community.hashi_vault/issues/340).
• The minimum version of hvac for community.hashi_vault is now 1.1.0 (https://github.com/ansible-collections/community.hashi_vault/issues/324).
• hashi_vault lookup - duplicate option entries in the term string now raises an exception instead of a warning (https://github.com/ansible-collections/community.hashi_vault/issues/356).

v4.2.1

Compare Source

======

Release Summary

This patch version updates the documentation for the vault_kv2_write module. There are no functional changes.

v4.2.0

Compare Source

======

Release Summary

This release contains a new module for KVv2 writes, and a new warning for duplicated term string options in the hashi_vault lookup.

Deprecated Features

• hashi_vault lookup - in v5.0.0 duplicate term string options will raise an exception instead of showing a warning (https://github.com/ansible-collections/community.hashi_vault/issues/356).

Bugfixes

• hashi_vault lookup - a term string with duplicate options would silently use the last value. The lookup now shows a warning on option duplication (https://github.com/ansible-collections/community.hashi_vault/issues/349).

New Modules

• vault_kv2_write - Perform a write operation against a KVv2 secret in HashiCorp Vault

v4.1.0

Compare Source

======

Release Summary

This release brings new generic vault_list plugins from a new contributor! There are also some deprecation notices for the next major version, and some updates to documentation attributes.

Deprecated Features

• ansible-core - support for ansible-core versions 2.11 and 2.12 will be dropped in collection version 5.0.0, making 2.13 the minimum supported version of ansible-core (https://github.com/ansible-collections/community.hashi_vault/issues/340).
• hvac - the minimum version of hvac to be supported in collection version 5.0.0 will be at least 1.0.2; this minimum may be raised before 5.0.0 is released, so please subscribe to the linked issue and look out for new notices in the changelog (https://github.com/ansible-collections/community.hashi_vault/issues/324).

New Plugins

Lookup

- vault_list - Perform a list operation against HashiCorp Vault

New Modules
-----------

- vault_list - Perform a list operation against HashiCorp Vault

v4.0.0

Compare Source

======

Release Summary

The next major version of the collection includes 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.

Minor Changes

• modules - all modules now document their action group and support for check mode in their attributes documentation (https://github.com/ansible-collections/community.hashi_vault/issues/197).

Breaking Changes / Porting Guide

• auth - the default value for token_validate has changed from true to false, as previously announced (https://github.com/ansible-collections/community.hashi_vault/issues/248).
• vault_kv2_get lookup - as previously announced, the default value for engine_mount_point in the vault_kv2_get lookup has changed from kv to secret (https://github.com/ansible-collections/community.hashi_vault/issues/279).

v3.4.0

Compare Source

======

Release Summary

This release includes a new module, fixes (another) requests header issue, and updates some inaccurate documentation. This is the last planned release before v4.0.0.

Minor Changes

• vault_pki_generate_certificate - the documentation has been updated to match the argspec for the default values of options alt_names, ip_sans, other_sans, and uri_sans (https://github.com/ansible-collections/community.hashi_vault/pull/318).

Bugfixes

• connection options - the namespace connection option will be forced into a string to ensure cmpatibility with recent requests versions (https://github.com/ansible-collections/community.hashi_vault/issues/309).

New Modules

• vault_kv2_delete - Delete one or more versions of a secret from HashiCorp Vault's KV version 2 secret store

v3.3.1

Compare Source

======

Release Summary

No functional changes in this release, this provides updated filter documentation for the public docsite.

v3.3.0

Compare Source

======

Release Summary

With the release of hvac version 1.0.0, we needed to update vault_token_create's support for orphan tokens. The collection's changelog is now viewable in the Ansible documentation site.

Minor Changes

• vault_token_create - creation or orphan tokens uses hvac's new v1 method for creating orphans, or falls back to the v0 method if needed (https://github.com/ansible-collections/community.hashi_vault/issues/301).

v3.2.0

Compare Source

======

Release Summary

This release brings support for the azure auth method, adds 412 to the default list of HTTP status codes to be retried, and fixes a bug that causes failures in token auth with requests>=2.28.0.

Minor Changes

• community.hashi_vault collection - add support for azure auth method, for Azure service principal, managed identity, or plain JWT access token (https://github.com/ansible-collections/community.hashi_vault/issues/293).
• community.hashi_vault retries - HTTP status code 412 <https://www.vaultproject.io/api-docs#&#8203;412>__ has been added to the default list of codes to be retried, for the new Server Side Consistent Token feature <https://www.vaultproject.io/docs/faq/ssct#q-is-there-anything-else-i-need-to-consider-to-achieve-consistency-besides-upgrading-to-vault-1-10>__ in Vault Enterprise (https://github.com/ansible-collections/community.hashi_vault/issues/290).

Bugfixes

• community.hashi_vault plugins - tokens will be cast to a string type before being sent to hvac to prevent errors in requests when values are AnsibleUnsafe (https://github.com/ansible-collections/community.hashi_vault/issues/289).
• modules - fix a "variable used before assignment" that cannot be reached but causes sanity test failures (https://github.com/ansible-collections/community.hashi_vault/issues/296).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot.