gcloud
GROUP
| COMMAND
[--account
=ACCOUNT
] [--billing-project
=BILLING_PROJECT
] [--configuration
=CONFIGURATION
] [--flags-file
=YAML_FILE
] [--flatten
=[KEY
,…]] [--format
=FORMAT
] [--help
] [--project
=PROJECT_ID
] [--quiet
, -q
] [--verbosity
=VERBOSITY
; default="warning"] [--version
, -v
] [-h
] [--access-token-file
=ACCESS_TOKEN_FILE
] [--impersonate-service-account
=SERVICE_ACCOUNT_EMAILS
] [--log-http
] [--trace-token
=TRACE_TOKEN
] [--no-user-output-enabled
]
gcloud
CLI manages authentication, local configuration, developer workflow, and interactions with the Google Cloud APIs.
For a quick introduction to the gcloud
CLI, a list of commonly used commands, and a look at how these commands are structured, run gcloud cheat-sheet
or see the `gcloud` CLI cheat sheet.
--account
=ACCOUNT
core/account
property value for this command invocation.
--billing-project
=BILLING_PROJECT
gcloud
. If you need to operate on one project, but need quota against a different project, you can use this flag to specify the billing project. If both billing/quota_project
and --billing-project
are specified, --billing-project
takes precedence. Run $ gcloud config set --help
to see more information about billing/quota_project
.
--configuration
=CONFIGURATION
gcloud topic configurations
. You can also use the CLOUDSDK_ACTIVE_CONFIG_NAME environment variable to set the equivalent of this flag for a terminal session.
--flags-file
=YAML_FILE
--flag
:value
dictionary. Useful for specifying complex flag values with special characters that work with any command interpreter. Additionally, each --flags-file
arg is replaced by its constituent flags. See $ gcloud topic flags-file for more information.
--flatten
=[KEY
,…]
name
[] output resource slices in KEY
into separate records for each item in each slice. Multiple keys and slices may be specified. This also flattens keys for --format
and --filter
. For example, --flatten=abc.def
flattens abc.def[].ghi
references to abc.def.ghi
. A resource record containing abc.def[]
with N elements will expand to N records in the flattened output. This allows us to specify what resource-key
the filter
will operate on. This flag interacts with other flags that are applied in this order: --flatten
, --sort-by
, --filter
, --limit
.
--format
=FORMAT
core/format
and --format
are specified, --format
takes precedence. --format
and core/format
both take precedence over core/default_format
. The supported formats are limited to: config
, csv
, default
, diff
, disable
, flattened
, get
, json
, list
, multi
, none
, object
, table
, text
, value
, yaml
. For more details run $ gcloud topic formats. Run $ gcloud config set --help
to see more information about core/format
--help
--project
=PROJECT_ID
gcloud config list --format='text(core.project)'
and can be set using gcloud config set project PROJECTID
.
--project
and its fallback core/project
property play two roles in the invocation. It specifies the project of the resource to operate on. It also specifies the project for API enablement check, quota, and billing. To specify a different project for quota and billing, use --billing-project
or billing/quota_project
property.
--quiet
, -q
gcloud
commands. If input is required, defaults will be used, or an error will be raised.
Overrides the default core/disable_prompts property value for this command invocation. This is equivalent to setting the environment variable CLOUDSDK_CORE_DISABLE_PROMPTS
to 1.
--verbosity
=VERBOSITY
; default="warning"
core/verbosity
property value for this command invocation. VERBOSITY
must be one of: debug
, info
, warning
, error
, critical
, none
.
--version
, -v
-h
--access-token-file
=ACCESS_TOKEN_FILE
gcloud
with an access token. The credentials of the active account (if exists) will be ignored. The file should only contain an access token with no other information. Overrides the default auth/access_token_file
property value for this command invocation.
--impersonate-service-account
=SERVICE_ACCOUNT_EMAILS
gcloud
invocation, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the impersonator, or a comma-separated list of service accounts to create an impersonation delegation chain. The impersonation is done without needing to create, download, and activate a key for the service account or accounts.
In order to make API requests as a service account, your currently selected account must have an IAM role that includes the iam.serviceAccounts.getAccessToken
permission for the service account or accounts.
The roles/iam.serviceAccountTokenCreator
role has the iam.serviceAccounts.getAccessToken permission
. You can also create a custom role.
You can specify a list of service accounts, separated with commas. This creates an impersonation delegation chain in which each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the roles/iam.serviceAccountTokenCreator
role on the next service account in the list. For example, when --impersonate-service-account=
,SERVICE_ACCOUNT_1
, the active account must have the SERVICE_ACCOUNT_2
roles/iam.serviceAccountTokenCreator
role on
, which must have the SERVICE_ACCOUNT_1
roles/iam.serviceAccountTokenCreator
role on
. SERVICE_ACCOUNT_2
is the impersonated service account and SERVICE_ACCOUNT_1
is the delegate.SERVICE_ACCOUNT_2
Overrides the default auth/impersonate_service_account
property value for this command invocation.
--log-http
core/log_http
property value for this command invocation.
--trace-token
=TRACE_TOKEN
core/trace_token
property value for this command invocation.
--user-output-enabled
core/user_output_enabled
property value for this command invocation. Use --no-user-output-enabled
to disable.
GROUP
is one of the following:
access-approval
access-context-manager
active-directory
ai
ai-platform
alloydb
alpha
(ALPHA)
Alpha versions of gcloud commands.
anthos
api-gateway
apigee
app
apphub
artifacts
asset
assured
audit-manager
auth
backup-dr
batch
beta
(BETA)
Beta versions of gcloud commands.
bigtable
billing
bms
bq
builds
certificate-manager
cloud-shell
cloudlocationfinder
colab
components
composer
compute
config
container
data-catalog
database-migration
dataflow
dataplex
dataproc
datastore
datastream
deploy
deployment-manager
developer-connect
dns
domains
edge-cache
edge-cloud
emulators
endpoints
essential-contacts
eventarc
filestore
firebase
firestore
functions
gemini
healthcare
iam
iap
identity
ids
immersive-stream
infra-manager
kms
logging
looker
lustre
managed-kafka
memcache
memorystore
metastore
migration
ml
model-armor
monitoring
netapp
network-connectivity
network-management
network-security
network-services
notebooks
observability
oracle-database
org-policies
organizations
pam
parametermanager
policy-intelligence
policy-troubleshoot
preview
(PREVIEW)
Preview versions of gcloud commands.
privateca
projects
publicca
pubsub
recaptcha
recommender
redis
resource-manager
run
scc
scheduler
secrets
service-directory
service-extensions
services
source
source-manager
spanner
sql
storage
tasks
telco-automation
topic
transcoder
transfer
vmware
workbench
workflows
workspace-add-ons
workstations
COMMAND
is one of the following:
cheat-sheet
docker
(DEPRECATED)
Enable Docker CLI access to Google Container Registry.
feedback
help
info
init
survey
version
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.5