-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update module github.com/hashicorp/vault/api to v1.15.0 #18
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/github.com-hashicorp-vault-api-1.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
changed the title
Update module github.com/hashicorp/vault/api to v1.9.2
Update module github.com/hashicorp/vault/api to v1.10.0
Sep 6, 2023
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
September 6, 2023 08:56
76bd3ba
to
da8df07
Compare
renovate
bot
changed the title
Update module github.com/hashicorp/vault/api to v1.10.0
Update module github.com/hashicorp/vault/api to v1.10.0 - autoclosed
Oct 23, 2023
renovate
bot
changed the title
Update module github.com/hashicorp/vault/api to v1.10.0 - autoclosed
Update module github.com/hashicorp/vault/api to v1.10.0
Oct 24, 2023
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
October 24, 2023 02:34
da8df07
to
b2b6619
Compare
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
January 25, 2024 02:46
b2b6619
to
145cc57
Compare
renovate
bot
changed the title
Update module github.com/hashicorp/vault/api to v1.10.0
Update module github.com/hashicorp/vault/api to v1.11.0
Jan 25, 2024
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
February 9, 2024 04:55
145cc57
to
7e3a61b
Compare
renovate
bot
changed the title
Update module github.com/hashicorp/vault/api to v1.11.0
Update module github.com/hashicorp/vault/api to v1.12.0
Feb 9, 2024
renovate
bot
changed the title
Update module github.com/hashicorp/vault/api to v1.12.0
Update module github.com/hashicorp/vault/api to v1.12.1
Mar 14, 2024
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
2 times, most recently
from
March 19, 2024 23:19
82f9181
to
5934f59
Compare
renovate
bot
changed the title
Update module github.com/hashicorp/vault/api to v1.12.1
Update module github.com/hashicorp/vault/api to v1.12.2
Mar 19, 2024
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
April 20, 2024 11:41
5934f59
to
7d44403
Compare
renovate
bot
changed the title
Update module github.com/hashicorp/vault/api to v1.12.2
Update module github.com/hashicorp/vault/api to v1.13.0
Apr 20, 2024
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
May 11, 2024 17:45
7d44403
to
dd822e2
Compare
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
May 24, 2024 02:27
dd822e2
to
3c127ce
Compare
renovate
bot
changed the title
Update module github.com/hashicorp/vault/api to v1.13.0
Update module github.com/hashicorp/vault/api to v1.14.0
May 24, 2024
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
June 6, 2024 11:29
3c127ce
to
70ec621
Compare
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
July 15, 2024 02:36
70ec621
to
0357138
Compare
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
September 10, 2024 20:34
0357138
to
b76a792
Compare
renovate
bot
changed the title
Update module github.com/hashicorp/vault/api to v1.14.0
Update module github.com/hashicorp/vault/api to v1.15.0
Sep 10, 2024
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
November 18, 2024 05:49
b76a792
to
bd31157
Compare
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-api-1.x
branch
from
December 23, 2024 02:56
bd31157
to
653ad46
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.9.1
->v1.15.0
Release Notes
hashicorp/vault (github.com/hashicorp/vault/api)
v1.15.0
Compare Source
1.15.0
September 27, 2023
SECURITY:
CHANGES:
which will have access to some system backend paths that were previously only accessible in the root namespace. [GH-21215]
data_path
will include full data path of secret, including name. [GH-22487]EventSender
interface method is nowSendEvent
instead ofSend
. [GH-22487]vault.rollback.attempt.{MOUNT_POINT}
andvault.route.rollback.{MOUNT_POINT}
metrics withvault.rollback.attempt
andvault.route.rollback metrics
by default. Added a telemetry configurationadd_mount_point_rollback_metrics
which, when set to true, causes vault to emit the metrics with mount points in their names. [GH-22400]FEATURES:
static roles on a defined schedule. [GH-22484]
IMPROVEMENTS:
#18257). Update go-kms-wrapping dependency to include PR
#155 [GH-22994]
use_sts_region_from_client
which allows for using dynamic regional sts endpoints based on Authorization header when using IAM-based authentication. [GH-21960]-dev-tls-san
flag to configure subject alternative names for the certificate generated when using-dev-tls
. [GH-22657]vault.policy.configured.count
. [GH-21010]-output-policy
recognition of some non-standard sudo paths [GH-21772]sys/raw/
andsys/leases/lookup/
to match prevailing conventions [GH-21760]CreateOperation
to be defined without anExistenceCheck
, thereby fixing misleadingx-vault-createSupported
in OpenAPI [GH-18492]service_account_json
parameter when reading DB connection details [GH-23256]pending_permits
,active_permits
, andpool_size
. [GH-21742]DEPRECATIONS:
BUG FIXES:
auth/token/create
fields to avoid incorrect warnings about ignored parameters [GH-18556]respects
AWS_ROLE_ARN
,AWS_WEB_IDENTITY_TOKEN_FILE
, andAWS_ROLE_SESSION_NAME
. [GH-21951]-field
flag is provided during avault write
. [GH-21546]table
. [GH-22818]policies are not used when Sentinel feature isn't licensed.
Also fix a related potential deadlock. [GH-21110]
identity/mfa/method/*
APIs [GH-20879]vault plugin runtime list
can successfully list plugin runtimes with GET [GH-23171]set of addrs changes.
sdk/ldaputil: use EscapeLDAPValue implementation from cap/ldap [GH-22249]
no managed key found with uuid
. [GH-21316]default_critical_options
anddefault_extension
if left unchanged. [GH-21739]ed25519
) [GH-21926]max_versions
default for secret metadata unintentionally overriding kv engine defaults [GH-22394]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
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 was generated by Mend Renovate. View the repository job log.