fix: Set up DirectPath e2e tests correctly #780
Merged
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.
In #770 we make the client to attempt DirectPath by default using the default spanner endpoint spanner.googleapis.com. However, currently DirectPath tests still need to use a custom endpoint aa423245250f2bbf.sandbox.googleapis.com, so we need to set it to a customChannelProvider, which will override the defaultChannelProvider in https://github.com/googleapis/java-spanner/blob/master/google-cloud-spanner/src/main/java/com/google/cloud/spanner/spi/v1/GapicSpannerRpc.java#L336. As a result, DirectPath tests can not be run properly. This PR fixes this problem by setting up the customChannelProvider properly.