mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-16 12:22:03 +00:00
gcloud: Wed Jun 8 09:13:38 UTC 2022
This commit is contained in:
parent
82063cbb03
commit
28d031b3c1
240 changed files with 3156 additions and 1115 deletions
|
|
@ -479,7 +479,7 @@ AVAILABLE PROPERTIES
|
|||
promote_by_default
|
||||
If True, when deploying a new version of a service, that version
|
||||
will be promoted to receive all traffic for the service. This
|
||||
property can be overridden via the --promote-by-default or
|
||||
property can be overridden with the --promote-by-default or
|
||||
--no-promote-by-default flags.
|
||||
|
||||
stop_previous_version
|
||||
|
|
@ -519,39 +519,35 @@ AVAILABLE PROPERTIES
|
|||
adds authentication to requests.
|
||||
|
||||
impersonate_service_account
|
||||
While set, 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. This is done without
|
||||
needing to create, download, and activate a key for the service
|
||||
account or accounts.
|
||||
While set, 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. This is done without needing to create, download,
|
||||
or 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.
|
||||
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.
|
||||
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 the property is set
|
||||
via `gcloud config set auth/impersonate-service-account=`
|
||||
`_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`,
|
||||
the active account must have the
|
||||
`roles/iam.serviceAccountTokenCreator` role on
|
||||
`_SERVICE_ACCOUNT_1_`, which must have the
|
||||
`roles/iam.serviceAccountTokenCreator` role on
|
||||
`_SERVICE_ACCOUNT_2_`.
|
||||
`_SERVICE_ACCOUNT_1_` is the impersonated service
|
||||
account and `_SERVICE_ACCOUNT_2_` is the delegate.
|
||||
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 the property is set through
|
||||
gcloud config set auth/impersonate_service_account=
|
||||
SERVICE_ACCOUNT_1,SERVICE_ACCOUNT_2, the active account must have
|
||||
the roles/iam.serviceAccountTokenCreator role on SERVICE_ACCOUNT_1,
|
||||
which must have the roles/iam.serviceAccountTokenCreator role on
|
||||
SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service
|
||||
account and SERVICE_ACCOUNT_2 is the delegate.
|
||||
|
||||
token_host
|
||||
Overrides the token endpoint to provision access tokens. It can be
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue