Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help

       gcloud  topic  configurations - supplementary help for named configura-

       Supplementary help for named configurations.

       gcloud properties can be	stored in named	configurations,	which are col-
       lections	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:

	 o Work	 with  multiple	projects. You can create a separate configura-
	   tion	for each project.

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

	 o 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 follow-
       ing 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	 prop-
       erty  values.  Inactive	configurations have no effect on gcloud	execu-

       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


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

	   If True, color will not be used when	printing messages in the  ter-

	   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.

	   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:

	   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	termi-
	   nal,	otherwise it is	available in the log files.

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

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

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


	   Set to local	to run docker build using a local docker installation,
	   or remote to	do the build on	a Google Compute Engine	VM.

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

	   If True, use	the Container Builder API to perform docker builds.


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

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


	   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.

	   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.


	   The name of the cluster to use by default when  working  with  Con-
	   tainer Engine.


	   The hostname	or IP address of your proxy server.

	   If  your  proxy  requires  authentication, the password to use when

	   The port to use when	connected to your proxy	server.

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

	   If  your  proxy  requires  authentication, the username to use when


NAME | DESCRIPTION | Creating configurations | Using configurations | AVAILABLE PROPERTIES

Want to link to this manual page? Use this URL:

home | help