The Gofer CLI accepts configuration through flags, environment variables, or configuration file.
When multiple configuration sources are used the hierarchy is (from lowest to highest) config file values -> environment variables -> flags. Meaning that if you give the same configurations different values through a configuration file and through flags, the value given in the flag will prevail.
You can view Gofer's global flags by simply typing
You can also set configuration values through environment variables. Each environment variable has a prefix
For example, setting your API token:
export GOFER_CLI_TOKEN=mysupersecrettoken gofer service token whoami
The most up to date list of possible environment variables exists here
Remember that any environment variable found within the above struct is prefixed with
GOFER_CLI_. So for example to set a new
hostvariable you would write:
For convenience reasons Gofer can also use a standard configuration file. The language of this file is HCL. Most of the options are simply in the form of
You can put your CLI configuration file in any of the following locations and Gofer will automatically detect and read from it(in order of first searched):
- The path given to the
The options available in the configuration file are the same as possible environment variables. To find the most up to date values you can use the code here. For convenience, a possible out of date list and explanation is listed below:
|namespace||string||The namespace ID of the namespace you'd like to default to. This is used to target specific namespaces when there might be multiple.|
|format||string||Can be one of three values: |
|host||string||The URL of the Gofer server; used to point the CLI and that correct host.|
|no_color||bool||Turns off color globally for all CLI commands.|
|token||string||The authentication token passed Gofer for Ident and Auth purposes.|
// /home/clintjedwards/.gofer.hcl namespace = "myNamespace" format = "pretty" host = "localhost:8080" no_color = false token = "mysupersecrettoken"