Bugfix: GCP multiple credentials specified error#741
Merged
Bobi-Wan merged 1 commit intogardener:mainfrom Jan 9, 2026
Merged
Conversation
this fixes the multiple credentials bug
gardener-robot
added
needs/review
gardener-robot
added
reviewed/lgtm
gardener-robot
added
the
status/closed
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.
What this PR does / why we need it:
The GCP API storage client introduced a bug related to multiple credentials options being used.
googleapis/google-cloud-go#13531
This bug is triggered with the key_file flow for GCP authentication.
This PR bumps google.golang.org/api v0.259.0 (and indirectly googleapis/google-api-go-client) to v0.259.0, which contains the bugfix.
Bugfix:
googleapis/google-api-go-client@2c33732
the bugfix is in the following release:
https://github.com/googleapis/google-api-go-client/releases/tag/v0.259.0
Bumping our local dependency (google.golang.org/api v0.259.0) fixes the issue as expected.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: