| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@schmidt-sebastian Can you take a look? |
Sorry, something went wrong.
|
Thanks for sending this over! The problem you described exists in both the CredentialsProvider and the ChannelProvider. I have opened a PR to deal with both: #3472 Let's leave this open until 3472 is approved. |
Sorry, something went wrong.
🤖 I have created a release *beep* *boop* --- <details><summary>2.51.1-SNAPSHOT</summary> ### Updating meta-information for bleeding-edge SNAPSHOT release. </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
Addresses #3458.
As of 0.52.0-beta, calls to setCredentials() on FirestoreOptions are effectively ignored. This is because GrpcTransportOptions.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.