Prefer provided credentials if they are present in FirestoreOptions #3460
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.
Addresses #3458.
As of 0.52.0-beta, calls to
setCredentials()
on FirestoreOptions are effectively ignored. This is becauseGrpcTransportOptions.setUpCredentialsProvider()
is no longer called in GrpcFirestoreRpc - instead the settings builder just pulls the credentials provider regardless of whether or not a fixed credential was supplied in the original options.It used to be:
Today it reads:
This was changed in #3320. (Diff line)
The call can be restored in the same class with some conditional logic, or the FirestoreOptions can try to return the correct CredentialsProvider.