feat: Use generic Google creds method to support Workload Identity Federation #99
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 switches from using google.JWTConfigFromJSON, which only supports JWT service account credentials. Instead it uses google.CredentialsFromJSONWithParams, which supports a variety of different credentials, including service accounts, gcloud user credentials, and Workflow Identity Federation configurations.
This fixes #66 and allows using Workflow Identity Federation, which allows calling from AWS to GCP without needing to provide a service account private key. This helps avoiding the need for credential rotation.