-
Notifications
You must be signed in to change notification settings - Fork 67
fix: DirectPath non-default SA requires creds #2281
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
Merged
Merged
Changes from 5 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
b836def
fix: DirectPath non-default SA requires creds
mohanli-ml 26cb584
fix: DirectPath non-default SA requires creds
mohanli-ml 15db7e8
fix: DirectPath non-default SA requires creds
mohanli-ml 1f389a9
Merge branch 'main' into dp-null-creds
mohanli-ml 33d5b82
fix: DirectPath non-default SA requires creds
mohanli-ml 5c0418b
fix: DirectPath non-default SA requires creds
mohanli-ml 1b97839
fix: DirectPath non-default SA requires creds
mohanli-ml File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should skip the whole DirectPath feature if
credentials
is null like you originally proposed? This would still fail the emulator tests in Spanner if directPath is enabled.For more context,
credentials
should never be null unless theCredentialProvider
is explicitly overridden to aNoCreentialsProvider
like this, which is probably what the Spanner tests did.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem here is that if the use case mentioned by @olavloite is valid, i.e., if customers set
.setCallCredentialsProvider(...).setCredentials(NoCredentials.getInstance())
, should we support it? My understanding is yes, but I do not know who should be the approver.About the spanner emulator test failure, I think the Spanner test should understand the environment and fix it in their repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we will take care of that (it's actually not the emulator tests, but some tests using a
MockSpannerService
implementation).That sounds reasonable to me. I think that it would be reasonable to instruct users who want to use DirectPath in combination with
CallCredentials
per RPC, that they have to supply a default set of credentials as well.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK I reverted the change back. PTAL. @blakeli0 @olavloite