feat: add GCS ServiceAccount support#1246
Merged
Slach merged 2 commits intoAltinity:masterfrom Sep 17, 2025
Merged
Conversation
Slach
approved these changes
Sep 17, 2025
Signed-off-by: Slach <bloodjazman@gmail.com>
Pull Request Test Coverage Report for Build 17786054696Details
💛 - Coveralls |
Collaborator
|
fixed #1173 |
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.
This PR adds support for using GCS ServiceAccounts instead of keys, when the default token source has the permission to impersonate the SA.
This is meant to be used inside Compute instances that have the necessary permission or inside Kubernetes clusters where the K8S ServiceAccount is linked to a ServiceAccount that can do the impersonation.