Add request_id to vault signed OCR response protos#2143
Merged
Conversation
✅ API Diff Results -
|
Include request_id on create, update, delete, and list secret response messages so vault nodes can bind signed OCR payloads to gateway requests.
prashantkumar1982
force-pushed
the
fix/vault-signed-response-request-id
branch
from
21d4503 to
7a28308
Compare
cedric-cordenier
previously approved these changes
Jun 11, 2026
…common into fix/vault-signed-response-request-id
russell-stern
approved these changes
Jun 11, 2026
jmank88
approved these changes
Jun 11, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Include request_id on create, update, delete, and list secret response messages so vault nodes can bind signed OCR payloads to gateway requests.