GCLOUD_TOPIC_CONFIGURATIONS(1)

NAME

gcloud topic configurations - supplementary help for named configurations

DESCRIPTION
gcloud properties can be stored in named configurations, which are collections of key-value pairs that influence the behavior of gcloud. Named configurations are intended to be an advanced feature, and you can probably ignore them entirely if you only work with one project. Properties that are commonly stored in configurations include default Google Compute Engine zone, verbosity level, project ID, and active user or service account. Configurations allow you to define and enable these and other settings together as a group. Configurations are especially useful if you:

    •   Work with multiple projects. You can create a separate configuration for each project.

    •   Use multiple accounts, for example, a user account and a service account, etc.

    •   Perform generally orthogonal tasks (work on an appengine app in project foo, administer a Google Compute Engine cluster in zone user-central-1a, manage the network configurations for region asia-east-1, etc.)

Property information stored in named configurations are readable by all gcloud commands and may be modified by gcloud config set and gcloud config unset.

Creating configurations
Named configurations maybe be defined by users or built into gcloud. User 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]*$ Additionally there is a builtin configuration named NONE that has no properties set. The easiest way to create a brand new configuration is by running
    $ gcloud init
This will guide you through setting up your first named configuration, creating a new named configuration, or reinitializing an existing named configuration. (Note: reinitializing an existing configuration will remove all its existing properties!) You can create a new empty configuration with
    $ gcloud config configurations create my-config

Using configurations
gcloud may have at most one active configuration which provides property values. Inactive configurations have no effect on gcloud executions. You can activate a configuration with
    $ gcloud config configurations activate my-config
You can view and change the properties of your active configuration using the following commands:
    $ gcloud config list $ gcloud config set
Additionally, commands under gcloud config configurations allow you to to list, activate, describe, and delete configurations that may or may not be active. You can activate a configuration for a single gcloud invocation using flag, --configuration my-config, or environment variable CLOUDSDK_ACTIVE_CONFIG_NAME=my-config.

AVAILABLE PROPERTIES

    core

        account
            The account gcloud should use for authentication. You can run gcloud auth list to see the accounts you currently have available.

        custom_ca_certs_file
            Absolute path to a custom CA cert file.

        default_regional_backend_service
            If True, backend services in gcloud compute backend-services will be regional by default. The --global flag will be required for global backend services.

        disable_color
            If True, color will not be used when printing messages in the terminal.

        disable_prompts
            If True, the default answer will be assumed for all user prompts. For any prompts that require user input, an error will be raised. This is the equivalent of using the global --quiet flag.

        disable_usage_reporting
            If True, anonymous statistics on SDK usage will not be collected. This is value is set based on your choices during installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics

        log_http
            If True, log HTTP requests and responses to the logs. You may need to adjust your verbosity setting if you want to see in the terminal, otherwise it is available in the log files.

        max_log_days
            Maximum number of days to retain log files before deleting. If set to 0, turns off log garbage collection and does not delete log files. If unset, defaults to 30.

        pass_credentials_to_gsutil
            If True, pass the configured Cloud SDK authentication to gsutil.

        project
            The project id of the Cloud Platform project to operate on by default. This can be overridden by using the global --project flag.

        trace_token
            Token used to route traces of service requests for investigation of issues. This token will be provided by Google support.

        user_output_enabled
            If False, messages to the user and command output on both standard output and standard error will be suppressed.

        verbosity
            The default logging verbosity for gcloud commands. This is the equivalent of using the global --verbosity flag.

    app

        cloud_build_timeout
            The timeout, in seconds, to wait for Docker builds to complete during deployments. All Docker builds now use the Container Builder API.

        stop_previous_version
            If True, when deploying a new version of a service, the previously deployed version is stopped. If False, older versions must be stopped manually.

    component_manager

        additional_repositories
            A comma separated list of additional repositories to check for components. This property is automatically managed by the gcloud components repositories commands.

        disable_update_check
            If True, the Cloud SDK will not automatically check for updates.

    compute

        region
            The default region to use when working with regional Compute Engine resources. When a --region flag is required but not provided, the command will fall back to this value, if set. To see valid choices, run gcloud compute regions list.

        zone
            The default zone to use when working with zonal Compute Engine resources. When a --zone flag is required but not provided, the command will fall back to this value, if set. To see valid choices, run gcloud compute zones list.

    container

        build_timeout
            The timeout, in seconds, to wait for container builds to complete.

        cluster
            The name of the cluster to use by default when working with Container Engine.

        use_application_default_credentials
            Use application default credentials to authenticate to the cluster API server.

        use_client_certificate
            Use the cluster's client certificate to authenticate to the cluster API server.

    functions

        region
            The default region to use when working with Google Compute functions resources. When a --region flag is required but not provided, the command will fall back to this value, if set. To see valid choices, run gcloud functions regions list.

    ml_engine

        polling_interval
            The interval (in seconds) at which to poll logs from your Cloud ML Engine jobs. Note that making it much faster than the default (60) will quickly use all of your quota.

    proxy

        address
            The hostname or IP address of your proxy server.

        password
            If your proxy requires authentication, the password to use when connecting.

        port
            The port to use when connected to your proxy server.

        type
            The type of proxy you are using. Supported proxy types are: [http, http_no_tunnel, socks4, socks5].

        username
            If your proxy requires authentication, the username to use when connecting.

    spanner

        instance
            The default instance to use when working with Cloud Spanner resources. When an instance is required but not provided by a flag, the command will fall back to this value, if set.