-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Always forward entity merge requests from perfStandby #24325
Merged
Merged
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
github-actions
bot
added
the
hashicorp-contributed-pr
If the PR is HashiCorp (i.e. not-community) contributed
label
Dec 1, 2023
CI Results: |
mpalmi
added
backport/1.13.x
Backport changes to `release/1.13.x`
backport/1.14.x
Backport changes to `release/1.14.x`
backport/1.15.x
Backport changes to `release/1.15.x`
labels
Dec 1, 2023
Build Results: |
elliesterner
approved these changes
Dec 1, 2023
mpalmi
added
backport/1.13.x
Backport changes to `release/1.13.x`
backport/1.14.x
Backport changes to `release/1.14.x`
backport/1.15.x
Backport changes to `release/1.15.x`
and removed
backport/1.13.x
Backport changes to `release/1.13.x`
backport/1.14.x
Backport changes to `release/1.14.x`
backport/1.15.x
Backport changes to `release/1.15.x`
labels
Dec 1, 2023
This was referenced Dec 1, 2023
elliesterner
pushed a commit
that referenced
this pull request
Dec 1, 2023
Update requests to /sys/identity/entity/merge perform merges on perfStandby nodes in memory and skip the persist call. This commit changes the behavior for the merge endpoint, forcing it to be forwarded from the standby to the active node. This change is specifically scoped to manual merges, as automatic merges are not isolated to a specific endpoint and require careful consideration for all callers.
mpalmi
added
backport/1.13.x
Backport changes to `release/1.13.x`
and removed
backport/1.13.x
Backport changes to `release/1.13.x`
labels
Dec 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport/1.13.x
Backport changes to `release/1.13.x`
backport/1.14.x
Backport changes to `release/1.14.x`
backport/1.15.x
Backport changes to `release/1.15.x`
hashicorp-contributed-pr
If the PR is HashiCorp (i.e. not-community) contributed
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.
Update requests to
/sys/identity/entity/merge
perform merges on perfStandby nodes in memory and skip the persist call.This PR changes the behavior for the merge endpoint, forcing it to be forwarded from the standby to the active node. This change is specifically scoped to manual merges, as automatic merges are not isolated to a specific endpoint and require careful consideration for all callers.
Tests are on Enterprise: https://github.com/hashicorp/vault-enterprise/pull/5008/files