fix(deps): update module github.com/hashicorp/vault/api to v1.9.0 #762
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.8.2
->v1.9.0
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
hashicorp/vault
v1.9.0
Compare Source
1.9.0
November 17, 2021
CHANGES:
been removed. [GH-12888]
specifying extensions when requesting ssh key signing. Update roles setting
allowed_extensions to
*
to permit any extension to be specified by an end-user. [GH-12847]FEATURES:
/
) and also on API endpoints (/v1/*
) [GH-12485]metadata endpoint. The data will be present in responses made to the data endpoint independent of the
calling token's
read
access to the metadata endpoint. [GH-12907]/<mount>/data/:path
kv-v2endpoint through HTTP
PATCH
. A newpatch
ACL capability has been added andis required to make such requests. [GH-12687]
local
auth mounts willgenerate identity entities for the tokens issued. The aliases of the entity
resulting from local auth mounts (local-aliases), will be scoped by the cluster.
This means that the local-aliases will never leave the geographical boundary of
the cluster where they were issued. This is something to be mindful about for
those who have implemented local auth mounts for complying with GDPR guidelines.
IMPROVEMENTS:
role/:name/secret-id-accessor/lookup
endpoint now returns a 404 status code when thesecret_id_accessor
cannot be found [GH-12788]skip_browser
CLI option to allow users to skip opening the default browser during the authentication flow. [GH-12876]allowed_policies_glob
anddisallowed_policies_glob
fields to token roles to allow glob matching of policies [GH-7277].well-known/keys
endpoint that are being used by roles to sign/verify tokens. [GH-12780]outstanding dirty pages that were not flushed. [GH-2093]
ed25519
as a key for the pki backend [GH-11780]external-source: "vault"
metadata value for Consul registration. [GH-12163]reference
field to batch items, and propogate it to the responseBUG FIXES:
unexpected fault address
panic when using persistent cache. [GH-12534]form_post
as theoidc_response_mode
. [GH-12265]prem
build.of dirty pages is 0. [GH-2093]
of dirty pages in the merkle tree at time of checkpoint creation. [GH-2093]
vault operator raft snapshot save
. [GH-12388]addr_type=public_v6
in auto-join [GH-12366]v1.8.3
Compare Source
1.8.3
29 September 2021
IMPROVEMENTS:
BUG FIXES:
unexpected fault address
panic when using persistent cache. [GH-12534]vault operator raft snapshot save
. [GH-12388]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: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.