actions-cli | GitHub Actions in real time | Continous Integration library

The gactions file you downloaded is the executable itself - not an installer or anything along those lines. You can put it somewhere in your PATH or call it directly by giving the full path when you're calling it, but it will not be automatically available unless you do so.

You can see your PATH with echo $PATH. If you wish, you can place it in one of those directories.

If you wish to continue to run it out of your Download directory (which I do, since I rarely use the command), you can open an iterm2 command line and call gactions with the full path:

Simply pipe all standard input from the parent process to the child and all output from the child to the parent.

The code below is a full wrapper around any shell command, with input/output/error redirection:

I don't think this is related to authentication of the tool. I believe that the project you're setting up does not have any versions of the action available. I tried with a number of my own projects:

~/Downloads/gactions list --project assistant-sdk-project

The PACKAGE_NAME field in this case is your actions.json file, or whatever you have called the Action definition package file. This is where you defined the entry point to your Action and describe how to access the fulfillment server.

My surmise is that github.com/gkaldevrel/cli/gactions/gactions.go:605 is calling .String() on a nil pointer to gabs.Container

The github.com/gkaldevrel/cli package doesn't seem to be public, so I can't tell for sure, but tracing through the stack trace and extrapolating from the different version of gabs.go at https://github.com/Jeffail/gabs/blob/master/gabs.go, it appears the gabs.Container has a func (g *Container) Bytes method that is trying to dereference g and is panicing because it's nil.

The documentation at https://developers.google.com/actions/reference/rest/Shared.Types/ConversationFulfillment states for the url parameter:

The HTTPS endpoint for the conversation (HTTP is not supported).

Additionally, the URL must be accessible from the public Internet (you don't show the full IP address, for good reason, so I can't tell if this is true or not).

Either way, you may be able to use something like ngrok to create an HTTPS endpoint and secure tunnel to your 35.189.x.x host. This will give you a public DNS entry and HTTPS endpoint. See also https://developers.google.com/actions/tools/ngrok for some details about using ngrok with Actions.