forked from hashicorp/vault
-
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
Upstream tag v1.18.3 (revision 7ae4eca540) #79
Open
fopina-ci
wants to merge
3,574
commits into
main
Choose a base branch
from
upstream-to-pr/rev-7ae4eca540
base: main
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
* [VAULT-30189] enos: verify identity and OIDC tokens Expand our baseline API and data verification by including the identity and identity OIDC tokens secrets engines. We now create a test entity, entity-alias, identity group, various policies, and associate them with the entity. For the OIDC side, we now configure the OIDC issuer, create and rotate named keys, create and associate roles with the named key, and issue and introspect tokens. During a second phase we also verify that the those some entities, groups, keys, roles, config, etc all exist with the expected values. This is useful to test durability after upgrades, migrations, etc. This change also includes new updates our prior `auth/userpass` and `kv` verification. We had two modules that were loosely coupled and interdependent. This restructures those both into a singular module with child modules and fixes the assumed values by requiring the read module to verify against the created state. Going forward we can continue to extend this secrets engine verification module with additional create and read checks for new secrets engines. Signed-off-by: Ryan Cragun <me@ryan.ec>
* Update vault-plugin-secrets-kv to v0.20.0 * Add changelog --------- Co-authored-by: hc-github-team-secure-vault-ecosystem <hc-github-team-secure-vault-ecosystem@users.noreply.github.com>
* Remove the BETA badge from EST * Add ent badge
Co-authored-by: Steven Clark <steven.clark@hashicorp.com>
Co-authored-by: Chelsea Shaw <82459713+hashishaw@users.noreply.github.com>
…o release/1.18.x (hashicorp#28352) * backport of commit abdeda4 * fix ent tests --------- Co-authored-by: Chelsea Shaw <82459713+hashishaw@users.noreply.github.com> Co-authored-by: Chelsea Shaw <cshaw@hashicorp.com>
Co-authored-by: Scott Miller <smiller@hashicorp.com>
Co-authored-by: Hamza Shili <98858609+HamzaShili65@users.noreply.github.com>
Co-authored-by: Angel Garbarino <Monkeychip@users.noreply.github.com>
Co-authored-by: Scott Miller <smiller@hashicorp.com>
…28376) Co-authored-by: claire bontempo <68122737+hellobontempo@users.noreply.github.com>
Co-authored-by: Rachel Culpepper <84159930+rculpepper@users.noreply.github.com>
…icorp#28387) * no-op commit due to failed cherry-picking * UI: stabilize replication tests (hashicorp#28384) * Add specificity to replication title selectors * Use specific selectors for replication titles in tests --------- Co-authored-by: temp <temp@hashicorp.com> Co-authored-by: Chelsea Shaw <82459713+hashishaw@users.noreply.github.com>
Co-authored-by: Steven Clark <steven.clark@hashicorp.com>
Co-authored-by: Chelsea Shaw <82459713+hashishaw@users.noreply.github.com>
Co-authored-by: Robert <17119716+robmonte@users.noreply.github.com>
Co-authored-by: Kuba Wieczorek <kuba.wieczorek@hashicorp.com>
Co-authored-by: Ellie <ellie.sterner@hashicorp.com>
Co-authored-by: Violet Hynes <violet.hynes@hashicorp.com>
Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com>
* bump webpack from 5.89 -> 5.94 * upgrade ember-svg-jar and kick yarn.lock * resolve micromatch to a patched version
Co-authored-by: Ryan Cragun <me@ryan.ec>
Co-authored-by: Brian Shumate <brianshumate@users.noreply.github.com>
Co-authored-by: Steven Clark <steven.clark@hashicorp.com>
Co-authored-by: Victor Rodriguez <vrizo@hashicorp.com>
Co-authored-by: Steven Clark <steven.clark@hashicorp.com>
…shicorp#29133) Co-authored-by: hc-github-team-secure-vault-core <github-team-secure-vault-core@hashicorp.com>
Co-authored-by: claire bontempo <68122737+hellobontempo@users.noreply.github.com>
Co-authored-by: Scott Miller <smiller@hashicorp.com>
Co-authored-by: Steven Clark <steven.clark@hashicorp.com>
Co-authored-by: helenfufu <25168806+helenfufu@users.noreply.github.com>
Co-authored-by: Ben Ash <32777270+benashz@users.noreply.github.com>
Co-authored-by: claire bontempo <68122737+hellobontempo@users.noreply.github.com>
Co-authored-by: Ben Ash <32777270+benashz@users.noreply.github.com>
Co-authored-by: kpcraig <3031348+kpcraig@users.noreply.github.com>
Co-authored-by: Thy Ton <maithytonn@gmail.com>
Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com>
Co-authored-by: Brian Shumate <brianshumate@users.noreply.github.com>
* Docs/secrets sync ssrf private endpoints (hashicorp#28746) * docs: add Secrets Sync SSRF protection breaking change to 1.17 upgrade guide The Secrets Sync feature in 1.17.3 introduced SSRF protection that blocks private IP ranges, affecting users accessing secret stores through private endpoints. This adds documentation about the change and available options. * renamed issue * referenced secret sync ssrf known issue * re-ordered secret sync known issue in page * Hide copy-to-clipboard button on the output example codeblock --------- Co-authored-by: yhyakuna <yoko@hashicorp.com> * Fix build issue --------- Co-authored-by: James <135497751+pixambi@users.noreply.github.com>
Co-authored-by: Adam Rowan <92474478+bear359@users.noreply.github.com>
Co-authored-by: Ken Keller <104874953+mister-ken@users.noreply.github.com>
Co-authored-by: Ken Keller <104874953+mister-ken@users.noreply.github.com>
Co-authored-by: mickael-hc <86245626+mickael-hc@users.noreply.github.com>
Co-authored-by: Yoko Hyakuna <yoko@hashicorp.com>
Co-authored-by: kitography <khaines@mit.edu>
Co-authored-by: Michael Blaum <96261585+hashiblaum@users.noreply.github.com> Co-authored-by: Tony Wittinger <anwittin@users.noreply.github.com>
Co-authored-by: F Team <jaisung.lee@fteam.kr>
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.
Integrating latest changes from hashicorp/vault tag v1.18.3
Commit summary omitted as it exceeds maximum message size.