CLI Usage

The gpcore CLI is organized into subcommands, each corresponding to a resource type such as project or node. Every subcommand supports further actions, and built-in help is available at every level so you do not need to refer back to this documentation for day-to-day use. Output is formatted as an ASCII table by default, but can be switched to JSON or CSV for piping into other tools.

The commandline tool is separated into subcommands. To get a list of all available subcommands, run gpcore help. To get help for a specific subcommand, run gpcore help <subcommand>.

As an example, to list all projects, run gpcore project list. If you run just the subcommand without any arguments, you will get a list of all available actions for that subcommand.

Some commands need flags or specific parameters. To get a list of all flags and parameters, run gpcore help <subcommand> <action>. For example, to change the active project, run gpcore project set-active --id <project-uuid>.

By default, the output is formatted as a ASCII table. If you want to pass the output to other tools for processing, you can append the flag --csv or --json. For example: gpcore project list --json | jq 'length'

Examples

testen wir mal