fix(deps): update module github.com/hashicorp/vault to v1.16.2 #62
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.2.1-0.20240208012854-90c1515f84d3
->v1.16.2
Release Notes
hashicorp/vault (github.com/hashicorp/vault)
v1.16.2
Compare Source
v1.16.1
Compare Source
1.16.1
April 04, 2024
Please note that Vault 1.16.1 is the first Enterprise release of the Vault Enterprise 1.16 series.
BUG FIXES:
v1.16.0
Compare Source
1.16.0
March 26, 2024
SECURITY:
client certificates to prevent trusting certs with the same serial number
but not the same public/private key. [GH-25649]
CHANGES:
enterprise
parameter to the/sys/health
endpoint [GH-24270]vault plugin reload
with-plugin
in the root namespace will now reload the plugin across all namespaces instead of just the root namespace. [GH-24878]vault plugin info
andvault plugin deregister
now require 2 positional arguments instead of accepting either 1 or 2. [GH-24250]enable_multiseal
in configuration.vault://{vault node}
[GH-24201]/identity/entity/merge
endpointare now always forwarded from standbys to the active node. [GH-24325]
database/config/:name
will now return a computedrunning_plugin_version
field if a non-builtin version is running. [GH-25105]Use the environment variable
VAULT_PLUGIN_USE_LEGACY_ENV_LAYERING=true
to opt out and keep higher preference for system environmentvariables. When this flag is set, Vault will check during unseal for conflicts and print warnings for any plugins with environment
variables that conflict with system environment variables. [GH-25128]
/sys/plugins/runtimes/catalog
response will always include a list of "runtimes" in the response, even if empty. [GH-24864]This includes github.com/docker/docker to v24.0.7+incompatible,
google.golang.org/grpc to v1.57.2 and golang.org/x/net to v0.17.0. [GH-23913]
FEATURES:
new installs of Vault. [GH-24382]
utilization reporting, which allows users to create manual exports of product-license [metering
data] to report to Hashicorp.
be changed without shutting down vault [GH-23571]
write-based HTTP methods and special-case
pki/issue
requests to preventoverloading the Vault server. [GH-25093]
IMPROVEMENTS:
tls-server-name
arg for plugin registration [GH-23549]mount_type
, returning mount information (e.g.kv
for KVV1/KVV2) for mount when appropriate. [GH-23047]the last heartbeat took, and the estimated clock skew between standby and
active node based on that heartbeat duration. [GH-24343]
auth/ldap: deprecates
connection_timeout
in favor ofrequest_timeout
for timeoutssdk/ldaputil: deprecates Client in favor of cap/ldap.Client [GH-22185]
authenticate_from_environment
variable to "true" and "false" string literals, too. [GH-22996]either provided arguments or retrieved HCP token through browser login. [GH-23897]
vault plugin
sub-commands. [GH-24250]vault operator usage
command output [GH-25751]plugin_tmpdir
config option for containerized plugins, in addition to the existingVAULT_PLUGIN_TMPDIR
environment variable. [GH-24978]the seal when unsealed, as well as the type of the recovery seal if an
auto-seal. [GH-23022]
disable_request_limiter
to allowdisabling the request limiter per-listener. [GH-25098]
code_challenge_methods_supported
to OpenID Connect Metadata [GH-24979]sys/plugins/reload/:type/:name
available in the root namespace for reloading a specific plugin across all namespaces. [GH-24878]entries rather than being limited to 62 like Consul is. Performance testing
shows improvements in throughput and latency under some write-heavy workloads.
listener config.
deletion_allowed
param to transformations and includetokenization
as a type option [GH-25436]BUG FIXES:
from two to one auto seal due to persistence of the previous seal type being
"multiseal". [GH-23573]
on the request. [GH-23861]
on the request. [GH-24256]
/sys/config/auditing
)will now force invalidation and be reloaded from storage when data is replicated
to other nodes.
log_requests_level
. [GH-24056]Vault is in seal migration mode. [GH-24165]
These can now be configured individually with
detect_deadlocks
. [GH-23902]support azure workload identities. [GH-24954]
partition could continue to write data to Consul after a new leader is elected
potentially causing data loss or corruption for keys with many concurrent
writers. For Enterprise clusters this could cause corruption of the merkle trees
leading to failure to complete merkle sync without a full re-index. [GH-23013]
{
[GH-24513]v1.16.0-rc3
Compare Source
1.16.0-rc3
March 13, 2024
SECURITY:
client certificates to prevent trusting certs with the same serial number
but not the same public/private key. [GH-25649]
CHANGES:
enterprise
parameter to the/sys/health
endpoint [GH-24270]vault plugin reload
with-plugin
in the root namespace will now reload the plugin across all namespaces instead of just the root namespace. [GH-24878]vault plugin info
andvault plugin deregister
now require 2 positional arguments instead of accepting either 1 or 2. [GH-24250]vault://{vault node}
[GH-24201]/identity/entity/merge
endpointare now always forwarded from standbys to the active node. [GH-24325]
database/config/:name
will now return a computedrunning_plugin_version
field if a non-builtin version is running. [GH-25105]Use the environment variable
VAULT_PLUGIN_USE_LEGACY_ENV_LAYERING=true
to opt out and keep higher preference for system environmentvariables. When this flag is set, Vault will check during unseal for conflicts and print warnings for any plugins with environment
variables that conflict with system environment variables. [GH-25128]
/sys/plugins/runtimes/catalog
response will always include a list of "runtimes" in the response, even if empty. [GH-24864]This includes github.com/docker/docker to v24.0.7+incompatible,
google.golang.org/grpc to v1.57.2 and golang.org/x/net to v0.17.0. [GH-23913]
FEATURES:
new installs of Vault. [GH-24382]
utilization reporting, which allows users to create manual exports of product-license [metering
data] to report to Hashicorp.
be changed without shutting down vault [GH-23571]
write-based HTTP methods and special-case
pki/issue
requests to preventoverloading the Vault server. [GH-25093]
IMPROVEMENTS:
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.