Closed vicly closed 3 years ago
I'm glad you have a solution that does work for you right now. gactions
does not support alternate authentication methods at the moment. However, in the Conversation Testing library you do create a service account and use that to run methods, so it may be possible to at some point use the underlying Actions API to authorize requests.
@Fleker, thanks for your response. The features of gaction
are quite useful in the automation area, it'll be great if it could support an alternative auth method in the future.
We'd like to run
gactions
CLI in CICD pipeline so to automatically publish the project defined in YAML files. To automate the process,gactions login
is tricky for us, is there any way to automate it?Our current solution is manually to copy
~/.credentials/gactions-actions.googleapis.com-go.json
to the agent machine, which is working, butgactions-actions.googleapis.com-go.json
is Google user-specific, a dedicated user for CICD is required => internal process + extra user managementgaction login
will invalidate the previous credentials => a risky point about human errorMay we know whether
gactions
support service account JSON file generated in GCP console or any other idea to solve this problem? Thanks.