[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[[["\u003cp\u003eNamed configurations in the gdcloud CLI store key-value pairs that define settings for different projects or organizational needs.\u003c/p\u003e\n"],["\u003cp\u003eConfigurations can be created using \u003ccode\u003egdcloud init\u003c/code\u003e or \u003ccode\u003egdcloud config configurations create [CONFIG_NAME]\u003c/code\u003e, allowing for user-defined or built-in settings.\u003c/p\u003e\n"],["\u003cp\u003eOnly one configuration can be active at a time, and it can be activated using \u003ccode\u003egdcloud config configurations activate [CONFIG_NAME]\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe properties of an active configuration can be viewed and modified using \u003ccode\u003egdcloud config list\u003c/code\u003e and \u003ccode\u003egdcloud config set\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eVarious properties can be stored in configurations, including project details, organization console URLs, and settings related to accessibility, authentication, and storage, among others.\u003c/p\u003e\n"]]],[],null,["# gdcloud topic configurations\n\nNAME\n----\n\ngdcloud topic configurations - Supplementary help for named configurations.\n\nDESCRIPTION\n-----------\n\ngdcloud CLI properties can be stored in named configurations, which are collections of key-value pairs that influence the behavior of gdcloud CLI.\nNamed configurations are beneficial if you manage more than one project or organization.\nProperties 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.\nConfiguration data is stored in `$HOME/.config/gdcloud/`.\nConfigurations are especially useful if you\n+ Work with multiple projects. You can create a separate configuration for each project.\n- Use multiple organization console URLs.\n\\* 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.\nProperty information stored in named configurations are readable by all gdcloud CLI commands. To set the properties, use the `gdcloud config set` command.\n\nCreate configurations\n---------------------\n\nNamed configurations can be defined by users or built into gdcloud CLI.\nUser-defined configurations have lowercase names, such as `johndoe`, `default`, `jeff-staging`, or `foo2`. These are defined by the following regular expression `^[a-z][-a-z0-9]*$`.\nTo create a new configuration, run \n\n gdcloud init\n\nThis 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.\n\nTo create a new empty configuration, run \n\n gdcloud config configurations create [CONFIG_NAME]\n\nUse configurations\n------------------\n\ngdcloud CLI should have at most one active configuration which provides property values. Inactive configurations have no effect on gdcloud CLI executions.\nTo activate a configuration, run \n\n gdcloud config configurations activate [CONFIG_NAME]\n\nTo view and change the properties of your active configuration, run \n\n gdcloud config list\n gdcloud config set\n\nAdditionally, commands under the `gdcloud config configurations` group let you list, activate, rename, describe, and delete configurations that might or might not be active.\n\nYou can activate a configuration for a single gdcloud invocation using flag `--configuration my-config`.\n\nAvailable Properties\n--------------------\n\n`accessibility`\n\\* `screen_reader`\n\\* If set, gdcloud CLI activates the screen reader.\n\n`auth`\n\\* `login_config_cert_path`\n\\* Path of the file that stores the current login configuration certificate.\n\n`component_manager`\n\\* `disable_update_check`\n\\* If set, gdcloud CLI does not automatically check for updates.\n\n`core`\n\\* `disable_prompts`\n\\* If True, the default answer is assumed for all user prompts. However, for any prompts that require user input, an error is raised.\n\\* `format`\n\\* Set the format for printing command output resources. The default is a command-specific human-friendly output format. If both `core/format` and `--format` are specified, `--format` takes precedence. The supported formats are limited to `csv`, `json`, `table`, `text`, `yaml`.\n\\* `organization_console_url`\n\\* URL to the current organization UI/console. Note that it should start with `https //console.`. For example, `https //console.org-name.gdch.google.com`.\n\\* `project`\n\\* Current project name.\n\n`storage`\n\\* `s3_access_key_id`\n\\* Access key ID of the S3 storage object. It is a unique identifier for users.\n\\* `s3_custom_ca_certs_file`\n\\* Custom certificates file for the S3 storage object.\n\\* `s3_endpoint`\n\\* The URL of the S3 object consists of `S3_ENDPOINT/$BUCKET_NAME/$OBJECT_NAME`. The `S3_ENDPOINT` is the location where the S3 storage bucket is located.\n\\* `s3_secret_access_key`\n\\* Private key of the S3 storage object that is used to sign requests."]]
