Update module github.com/hashicorp/vault/api to v1.14.0 #602
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
added
dependencies
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
90665d8
to
e63357b
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.12.2->v1.14.0Release Notes
hashicorp/vault (github.com/hashicorp/vault/api)
v1.14.0Compare 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_templateconfiguration stanza. The process-supervisor configuration can be generated with a newvault agent generate-confighelper 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]
reloadoption 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 thepathoption, and theremove_jwt_after_readingconfig option is set to true (default). [GH-18863]results in a response which contains the full billing period [GH-20694]
/sys/internal/counters/configendpoint now contains read-onlyminimum_retention_months. [GH-20150]/sys/internal/counters/configendpoint now contains read-onlyreporting_enabledandbilling_start_timestampfields. [GH-20086]auth/kerberos: Upgrade plugin dependencies [GH-20771]
VAULT_PPROF_WRITE_TO_FILE=trueis set on the server. [GH-20609]reporting via the
OPTOUT_LICENSE_REPORTINGenvironment variable. [GH-3939]secrets/gcpkms: Upgrade plugin dependencies [GH-20784]
kv-getcommand for reading kv v2 data and metadata [GH-20590]BUG FIXES:
max_page_sizeproperly [GH-20453]on this secondary if we don't have a corresponding mount entry.
new_tokenforwarding 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.sscGenCounterresulting 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]
TypeInt64schema 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_allto persist after deselecting all operation checkboxes [GH-19139]v1.13.0Compare Source
1.13.0
March 01, 2023
SECURITY:
secret is unsupported by this backendwill be thrown by the lease manager. [GH-18874]CHANGES:
rolefield on login [GH-19005]This will only be used internally for implementing user lockout. [GH-17104]
Plugins using sdk/useragent.String must instead use sdk/useragent.PluginString. [GH-14229]
builtinin their metadata remain unaffected. [GH-18051]GET /database/config/:nameendpoint now returns an additionalplugin_versionfield in the response data. [GH-16982]GET /sys/auth/:path/tuneandGET /sys/mounts/:path/tuneendpoints may now return an additionalplugin_versionfield in the response data if set. [GH-17167]GETfor/sys/auth,/sys/auth/:path,/sys/mounts, and/sys/mounts/:pathpaths now return additionalplugin_version,running_plugin_versionandrunning_sha256fields in the response data for each mount. [GH-17167]FEATURES:
synchronized across primary and performance replica clusters offering
a unified CRL/OCSP view of revocations across cluster boundaries. [GH-19196]
brute force attacks for userpass, approle and ldap auth methods. [GH-19230]
sys/config/group-policy-applicationAPI, policies can be configured to apply outside of namespace hierarchy, allowing this kind of cross-namespace sharing.IMPROVEMENTS:
token_fileauto-auth configuration to allow using a pre-existing token for Vault Agent. [GH-18740]metrics_onlyrole, serving only metrics, as part of the listener's new top levelroleoption. [GH-18101]elide_list_responsesoption, providing a countermeasure for a common source of oversized audit log entries [GH-18128]Virtual Machine Scale Set (VMSS) in flexible orchestration mode. [GH-17540]
abort_on_errorparameter to CLI login command to help in non-interactive contexts [GH-19076]Make passcode arguments consistent across login MFA method types. [GH-18610]
vault operator rekeyprompts to describe recovery keys when-target=recovery[GH-18892]temporary file for SIGUSR2 signals. [GH-17929]
events.alpha1experiment. [GH-18682]sys/loggersandsys/loggers/:nameendpoints [GH-17979]sys/lockedusers/[mount_accessor]/unlock/[alias_identifier] to sys/locked-users/[mount_accessor]/unlock/[alias_identifier]. [GH-18675]
with given mount_accessor and alias_identifier if locked [GH-18279]
detect_deadlocksconfig to optionally detect core state deadlocks [GH-18604]vault operator migratein order to speed up a migration. [GH-18817]sys/config/group-policy-application, to allow group policies to be configurableto apply to a group in
anynamespace. The default,within_namespace_hierarchy, is the current behaviour.{mountPath}to{<type>_mount_path}[GH-18663]vX.Y.Z+builtinorvX.Y.Z+builtin.vault. [GH-17289]deactivated state if this is not the first unseal after an upgrade. [GH-17879]
tls_server_nameandtls_skip_verifyparameters [GH-18799]allowed by role [GH-18397]
default_follows_latest_issuer. [GH-17824]config/auto-tidy,config/crl, androles/:role. [GH-18222]which is repeated on batch responses to help more easily correlate inputs with outputs. [GH-18243]
retry_join_as_non_voterconfig option. [GH-18030]go.opentelemetry.io/otel,go.opentelemetry.io/otel/sdk,go.opentelemetry.io/otel/traceto v1.11.2 [GH-18589]DEPRECATIONS:
BUG FIXES:
token_bound_cidrsvalidation when using /32 blocks for role and secret ID [GH-18145]-mountflag and secret key path are the same. [GH-17679]vault secrets list -detailedoutput. [GH-17577]vault servercommand will no longer prevent startup. Instead, a warning will bConfiguration
📅 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.