fix(spanner): enforce only one resource header#12618
Merged
Conversation
Only one resource header (google-cloud-resource-prefix) should be included in requests that are sent to Spanner. If the context that is used for a request already contains a resource header, then that header value will be removed, and only the resource header that is set by the Spanner client will be included in the request.
rahul2393
approved these changes
Jul 30, 2025
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.
Only one resource header (google-cloud-resource-prefix) should be included in requests that are sent to Spanner. If the context that is used for a request already contains a resource header, then that header value will be removed, and only the resource header that is set by the Spanner client will be included in the request.