fix(deps): update module github.com/hashicorp/vault/api to v1.14.0 - autoclosed #76
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.13.0
->v1.14.0
Release Notes
hashicorp/vault (github.com/hashicorp/vault/api)
v1.14.0
Compare Source
1.14.0
June 21, 2023
BREAKING CHANGES:
To re-enable keeping these metrics available on the tidy status endpoint, enable
maintain_stored_certificate_counts on tidy-config, to also publish them to the
metrics consumer, enable publish_stored_certificate_count_metrics . [GH-18186]
CHANGES:
that allows for setting of the primary cluster addresses directly, instead of
via a token.
FEATURES:
utilization reporting, which sends minimal product-license metering
data
to HashiCorp without requiring you to manually collect and report them.
env_template
configuration stanza. The process-supervisor configuration can be generated with a newvault agent generate-config
helper tool. [GH-20530]as an external plugin by vault versions that support secrets/auth plugin
multiplexing (> 1.12) [GH-19215]
vault proxy -config=config.hcl
. It currently has the same feature set as Vault Agent's API proxy, but the two may diverge in the future. We plan to deprecate the API proxy functionality of Vault Agent in a future release. [GH-20548]IMPROVEMENTS:
distinguishing client sources. [GH-20626]
reload
option to cert auth configuration in case of external renewals of local x509 key-pairs. [GH-19002]remove_jwt_follows_symlinks
(default: false), that, if set to true will now remove the JWT, instead of the symlink to the JWT, if a symlink to a JWT has been provided in thepath
option, and theremove_jwt_after_reading
config option is set to true (default). [GH-18863]results in a response which contains the full billing period [GH-20694]
/sys/internal/counters/config
endpoint now contains read-onlyminimum_retention_months
. [GH-20150]/sys/internal/counters/config
endpoint now contains read-onlyreporting_enabled
andbilling_start_timestamp
fields. [GH-20086]auth/kerberos: Upgrade plugin dependencies [GH-20771]
VAULT_PPROF_WRITE_TO_FILE=true
is set on the server. [GH-20609]reporting via the
OPTOUT_LICENSE_REPORTING
environment variable. [GH-3939]secrets/gcpkms: Upgrade plugin dependencies [GH-20784]
kv-get
command for reading kv v2 data and metadata [GH-20590]BUG FIXES:
max_page_size
properly [GH-20453]on this secondary if we don't have a corresponding mount entry.
new_token
forwarding is set. When this occurred, this would result in the following error to the client:error performing token check: no lease entry found for token that ought to have one, possible eventual consistency issue
.sscGenCounter
resulting in 412 errors.
have its own changelog entry. Fix wrong lock used in ListAuths link meta interface implementation. [GH-21260]
a performance secondary. This resulted in the data being set to nil in the cache
and a "invalid value" error being returned from the API.
break replication.
with a new entity alias to be incorrectly forwarded from perf standbys. [GH-21100]
TypeInt64
schema field. [GH-18729]secrets/transit: Fix bug related to shorter dedicated HMAC key sizing.
sdk/helper/keysutil: New HMAC type policies will have HMACKey equal to Key and be copied over on import. [GH-20864]
operation_all
to persist after deselecting all operation checkboxes [GH-19139]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.