1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 20:36:39 +00:00

gcloud: Wed Mar 15 11:22:01 UTC 2023

This commit is contained in:
Automated 2023-03-15 11:22:01 +00:00
parent 29661f002c
commit a4bd29dd06
164 changed files with 2541 additions and 844 deletions

View file

@ -4,13 +4,11 @@ NAME
SYNOPSIS
gcloud beta run jobs add-iam-policy-binding JOB --member=PRINCIPAL
--role=ROLE [--region=REGION]
[--condition=[KEY=VALUE,...]
| --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...]
--role=ROLE [--region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Add an IAM policy binding to the IAM policy of a Cloud Run job. One
binding consists of a member, a role, and an optional condition.
binding consists of a member, and a role.
EXAMPLES
To add an IAM policy binding for the role of 'roles/run.invoker' for the
@ -20,17 +18,6 @@ EXAMPLES
--region='us-central1' --member='user:test-user@gmail.com' \
--role='roles/run.invoker'
To add an IAM policy binding which expires at the end of the year 2019 for
the role of 'roles/run.invoker' and the user 'test-user@gmail.com' with job
'my-job' and region 'us-central1', run:
$ gcloud beta run jobs add-iam-policy-binding my-job \
--region='us-central1' --member='user:test-user@gmail.com' \
--role='roles/run.invoker' \
--condition='expression=request.time <
timestamp("2020-01-01T00:00:00Z"),title=expires_end_of_2019,descrip\
tion=Expires at midnight on 2019-12-31'
See https://cloud.google.com/iam/docs/managing-policies for details of
policy role and member types.
@ -83,43 +70,6 @@ OPTIONAL FLAGS
Region in which the resource can be found. Alternatively, set the
property [run/region].
At most one of these can be specified:
--condition=[KEY=VALUE,...]
A condition to include in the binding. When the condition is
explicitly specified as None (--condition=None), a binding without a
condition is added. When the condition is specified and is not None,
--role cannot be a basic role. Basic roles are roles/editor,
roles/owner, and roles/viewer. For more on conditions, refer to the
conditions overview guide:
https://cloud.google.com/iam/docs/conditions-overview
When using the --condition flag, include the following key-value
pairs:
expression
(Required) Condition expression that evaluates to True or False.
This uses a subset of Common Expression Language syntax.
If the condition expression includes a comma, use a different
delimiter to separate the key-value pairs. Specify the delimiter
before listing the key-value pairs. For example, to specify a
colon (:) as the delimiter, do the following:
--condition=^:^title=TITLE:expression=EXPRESSION. For more
information, see
https://cloud.google.com/sdk/gcloud/reference/topic/escaping.
title
(Required) A short string describing the purpose of the
expression.
description
(Optional) Additional description for the expression.
--condition-from-file=CONDITION_FROM_FILE
Path to a local JSON or YAML file that defines the condition. To see
available fields, see the help for --condition.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

View file

@ -4,13 +4,11 @@ NAME
SYNOPSIS
gcloud beta run jobs remove-iam-policy-binding JOB --member=PRINCIPAL
--role=ROLE [--region=REGION]
[--all | --condition=[KEY=VALUE,...]
| --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...]
--role=ROLE [--region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Remove an IAM policy binding from the IAM policy of a job. One
binding consists of a member, a role, and an optional condition.
binding consists of a member, and a role.
EXAMPLES
To remove an IAM policy binding for the role of 'roles/run.invoker' for the
@ -21,17 +19,6 @@ EXAMPLES
--region='us-central1' --member='user:test-user@gmail.com' \
--role='roles/run.invoker'
To remove an IAM policy binding which expires at the end of the year 2019
for the role of 'roles/run.invoker' and the user 'test-user@gmail.com' with
job 'my-job' and region 'us-central1', run:
$ gcloud beta run jobs remove-iam-policy-binding my-job \
--region='us-central1' --member='user:test-user@gmail.com' \
--role='roles/run.invoker' \
--condition='expression=request.time <
timestamp("2020-01-01T00:00:00Z"),title=expires_end_of_2019,descrip\
tion=Expires at midnight on 2019-12-31'
See https://cloud.google.com/iam/docs/managing-policies for details of
policy role and member types.
@ -85,47 +72,6 @@ OPTIONAL FLAGS
Region in which the resource can be found. Alternatively, set the
property [run/region].
At most one of these can be specified:
--all
Remove all bindings with this role and principal, irrespective of any
conditions.
--condition=[KEY=VALUE,...]
The condition of the binding that you want to remove. When the
condition is explicitly specified as None (--condition=None), a
binding without a condition is removed. Otherwise, only a binding
with a condition that exactly matches the specified condition
(including the optional description) is removed. For more on
conditions, refer to the conditions overview guide:
https://cloud.google.com/iam/docs/conditions-overview
When using the --condition flag, include the following key-value
pairs:
expression
(Required) Condition expression that evaluates to True or False.
This uses a subset of Common Expression Language syntax.
If the condition expression includes a comma, use a different
delimiter to separate the key-value pairs. Specify the delimiter
before listing the key-value pairs. For example, to specify a
colon (:) as the delimiter, do the following:
--condition=^:^title=TITLE:expression=EXPRESSION. For more
information, see
https://cloud.google.com/sdk/gcloud/reference/topic/escaping.
title
(Required) A short string describing the purpose of the
expression.
description
(Optional) Additional description for the expression.
--condition-from-file=CONDITION_FROM_FILE
Path to a local JSON or YAML file that defines the condition. To see
available fields, see the help for --condition.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

View file

@ -5,15 +5,13 @@ NAME
SYNOPSIS
gcloud beta run services add-iam-policy-binding SERVICE --member=PRINCIPAL
--role=ROLE [--platform=PLATFORM; default="managed"]
[--condition=[KEY=VALUE,...]
| --condition-from-file=CONDITION_FROM_FILE]
[--region=REGION
| --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION
| --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Add an IAM policy binding to the IAM policy of a Cloud Run service.
One binding consists of a member, a role, and an optional condition.
One binding consists of a member, and a role.
EXAMPLES
To add an IAM policy binding for the role of 'roles/run.invoker' for the
@ -24,17 +22,6 @@ EXAMPLES
--region='us-central1' --member='user:test-user@gmail.com' \
--role='roles/run.invoker'
To add an IAM policy binding which expires at the end of the year 2019 for
the role of 'roles/run.invoker' and the user 'test-user@gmail.com' with
service 'my-service' and region 'us-central1', run:
$ gcloud beta run services add-iam-policy-binding my-service \
--region='us-central1' --member='user:test-user@gmail.com' \
--role='roles/run.invoker' \
--condition='expression=request.time <
timestamp("2020-01-01T00:00:00Z"),title=expires_end_of_2019,descrip\
tion=Expires at midnight on 2019-12-31'
See https://cloud.google.com/iam/docs/managing-policies for details of
policy role and member types.
@ -100,43 +87,6 @@ OPTIONAL FLAGS
--kubeconfig and --context flags to specify a kubeconfig file and
the context for connecting.
At most one of these can be specified:
--condition=[KEY=VALUE,...]
A condition to include in the binding. When the condition is
explicitly specified as None (--condition=None), a binding without a
condition is added. When the condition is specified and is not None,
--role cannot be a basic role. Basic roles are roles/editor,
roles/owner, and roles/viewer. For more on conditions, refer to the
conditions overview guide:
https://cloud.google.com/iam/docs/conditions-overview
When using the --condition flag, include the following key-value
pairs:
expression
(Required) Condition expression that evaluates to True or False.
This uses a subset of Common Expression Language syntax.
If the condition expression includes a comma, use a different
delimiter to separate the key-value pairs. Specify the delimiter
before listing the key-value pairs. For example, to specify a
colon (:) as the delimiter, do the following:
--condition=^:^title=TITLE:expression=EXPRESSION. For more
information, see
https://cloud.google.com/sdk/gcloud/reference/topic/escaping.
title
(Required) A short string describing the purpose of the
expression.
description
(Optional) Additional description for the expression.
--condition-from-file=CONDITION_FROM_FILE
Path to a local JSON or YAML file that defines the condition. To see
available fields, see the help for --condition.
Arguments to locate resources, depending on the platform used.
At most one of these can be specified:

View file

@ -5,15 +5,13 @@ NAME
SYNOPSIS
gcloud beta run services remove-iam-policy-binding SERVICE
--member=PRINCIPAL --role=ROLE [--platform=PLATFORM; default="managed"]
[--all | --condition=[KEY=VALUE,...]
| --condition-from-file=CONDITION_FROM_FILE]
[--region=REGION
| --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION
| --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Remove an IAM policy binding from the IAM policy of a service. One
binding consists of a member, a role, and an optional condition.
binding consists of a member, and a role.
EXAMPLES
To remove an IAM policy binding for the role of 'roles/run.invoker' for the
@ -24,17 +22,6 @@ EXAMPLES
--region='us-central1' --member='user:test-user@gmail.com' \
--role='roles/run.invoker'
To remove an IAM policy binding which expires at the end of the year 2019
for the role of 'roles/run.invoker' and the user 'test-user@gmail.com' with
service 'my-service' and region 'us-central1', run:
$ gcloud beta run services remove-iam-policy-binding my-service \
--region='us-central1' --member='user:test-user@gmail.com' \
--role='roles/run.invoker' \
--condition='expression=request.time <
timestamp("2020-01-01T00:00:00Z"),title=expires_end_of_2019,descrip\
tion=Expires at midnight on 2019-12-31'
See https://cloud.google.com/iam/docs/managing-policies for details of
policy role and member types.
@ -101,47 +88,6 @@ OPTIONAL FLAGS
--kubeconfig and --context flags to specify a kubeconfig file and
the context for connecting.
At most one of these can be specified:
--all
Remove all bindings with this role and principal, irrespective of any
conditions.
--condition=[KEY=VALUE,...]
The condition of the binding that you want to remove. When the
condition is explicitly specified as None (--condition=None), a
binding without a condition is removed. Otherwise, only a binding
with a condition that exactly matches the specified condition
(including the optional description) is removed. For more on
conditions, refer to the conditions overview guide:
https://cloud.google.com/iam/docs/conditions-overview
When using the --condition flag, include the following key-value
pairs:
expression
(Required) Condition expression that evaluates to True or False.
This uses a subset of Common Expression Language syntax.
If the condition expression includes a comma, use a different
delimiter to separate the key-value pairs. Specify the delimiter
before listing the key-value pairs. For example, to specify a
colon (:) as the delimiter, do the following:
--condition=^:^title=TITLE:expression=EXPRESSION. For more
information, see
https://cloud.google.com/sdk/gcloud/reference/topic/escaping.
title
(Required) A short string describing the purpose of the
expression.
description
(Optional) Additional description for the expression.
--condition-from-file=CONDITION_FROM_FILE
Path to a local JSON or YAML file that defines the condition. To see
available fields, see the help for --condition.
Arguments to locate resources, depending on the platform used.
At most one of these can be specified: