gdcloud topic configurations - Supplementary help for named configurations.
gdcloud CLI properties can be stored in named configurations, which are collections of key-value pairs that influence the behavior of gdcloud CLI.
Named configurations are beneficial if you manage more than one project or organization.
Properties commonly stored in configurations include the organization console URL and project ID. Configurations let you define and enable these and other settings together as a group.
Configuration data is stored in
Configurations are especially useful if you
+ Work with multiple projects. You can create a separate configuration for each project.
- Use multiple organization console URLs.
* Perform generally independent tasks For example, one configuration can be used to work on the Object Storage service in one project and manage an unrelated service in another project.
Property information stored in named configurations are readable by all gdcloud CLI commands. To add more properties, use the
gdcloud config set command.
Named configurations can be defined by users or built into gdcloud CLI.
User-defined configurations have lowercase names, such as
foo2. These are defined by the following regular expression
To create a new configuration, run
This guides you through setting up your first named configuration, creating a new named configuration, or reinitializing an existing named configuration. Note that reinitializing an existing configuration removes all its existing properties.
To create a new empty configuration, run
gdcloud config configurations create [CONFIG_NAME]
gdcloud CLI should have at most one active configuration which provides property values. Inactive configurations have no effect on gdcloud CLI executions. To activate a configuration, run
gdcloud config configurations activate [CONFIG_NAME]
To view and change the properties of your active configuration, run
gdcloud config list
gdcloud config set
Additionally, commands under the
gdcloud config configurations group let you list, activate, rename, describe, and delete configurations that might or might not be active.
* If set, gdcloud CLI activates the screen reader.
* Path of the file that stores the current login configuration certificate.
* If set, gdcloud CLI does not automatically check for updates.
* URL to the current GDCH organization UI/console. Note that it should start with
https //console.. For example,
* Current GDCH project name.
* Access key ID of the S3 storage object. It is a unique identifier for users.
* Private key of the S3 storage object that is used to sign requests.
* Custom certificates file for the S3 storage object.
* The URL of the S3 object consists of
S3_ENDPOINT is the location where the S3 storage bucket is located.