SK-2824 Request headers support#304
Merged
Merged
Conversation
Devesh-Skyflow
approved these changes
May 14, 2026
saileshwar-skyflow
approved these changes
May 14, 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
3 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.
Why:
Previously there was no way to pass custom headers at the request level. This change adds that capability while keeping the API minimal and type-safe.
Batch processing in the SDK is handled internally — a single bulkInsert call may fan out into multiple HTTP requests. There was no mechanism for callers
to:
Attach custom headers (e.g. x-request-id) to vault API calls
Generate a unique header value per batch (e.g. unique request IDs for tracing)