Open alexeyinkin opened 7 months ago
Ran into the same issue. Looking at the code it seems there is a check for this and throws the ArgumentError but the actual type is never used by the code.
I wonder if there are some restrictions in GCP or could this check simply be removed?
Edit: No these are indeed very different ways to authenticate and the block above is needed for the current way the package is authenticating in.
I try to run an app from a GitHub workflow. It needs to communicate with Google Cloud. The workflow uses Workload Identity Federation to authenticate. It produces a key of the type
external_account
whilegoogleapis_auth
currently only handles the typeservice_account
.Given that Workflow Identity Federation is the recommended way to access Google Cloud resources, I think this should be fixed.
Steps to Reproduce
1. Create a project and configure Workload Identity Federation:
2. Create a Dart app
pubspec.yaml:
main.dart:
3. Set up the workflow
Create the repository variables:
PROJECT_NAME
,PROJECT_NUMBER
.The workflow:
4. Run the workflow
Expected
No error
Actual