gcloud alpha pubsub topics add-iam-policy-binding - add IAM policy binding to a topic

gcloud alpha pubsub topics add-iam-policy-bindingTOPIC--member=PRINCIPAL--role=ROLE[--condition=[KEY=VALUE,…]    |--condition-from-file=PATH_TO_FILE][GCLOUD_WIDE_FLAG …]

gcloudalphapubsubtopicsadd-iam-policy-bindingmy-topic--member='user:test-user@example.com'--role='roles/editor'

To add an IAM policy binding with the role of 'roles/editor' for the serviceaccount 'my-iam-account@my-project.iam.gserviceaccount.com' on the topic'my-topic', run:

gcloudalphapubsubtopicsadd-iam-policy-bindingmy-topic--member='serviceAccount:my-iam-account@my-project.iam.gserviceaccount.com'--role='roles/editor'

To add an IAM policy binding which expires at the end of the year 2018 for therole of 'roles/pubsub.publisher' and the user 'test-user@example.com' with topic'my-topic', run:

gcloudalphapubsubtopicsadd-iam-policy-bindingmy-topic--member='user:test-user@example.com'--role='roles/pubsub.publisher'--condition='expression=request.time< timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\tion=Expires at midnight on 2018-12-31'

Seehttps://cloud.google.com/iam/docs/managing-policiesfor details of policy role and member types.

Topic resource - The topic to add the IAM policy binding. This represents aCloud resource. (NOTE) Some attributes are not given arguments in this group butcan be set in other ways.

To set theproject attribute:

• provide the argumenttopic on the command line with a fullyspecified name;
• provide the argument--project on the command line;
• set the propertycore/project.

This must be specified.

TOPIC

ID of the topic or fully qualified identifier for the topic.

To set thetopic attribute:

• provide the argumenttopic on the command line.

--member=PRINCIPAL

The principal to add the binding for. Should be of the formuser|group|serviceAccount:email ordomain:domain.

Examples:user:test-user@gmail.com,group:admins@example.com,serviceAccount:test123@example.domain.com, ordomain:example.domain.com.

Some resources also accept the following special values:

• allUsers - Special identifier that represents anyone who is on theinternet, with or without a Google account.
• allAuthenticatedUsers - Special identifier that represents anyonewho is authenticated with a Google account or a service account.

--role=ROLE

Role name to assign to the principal. The role name is the complete path of apredefined role, such asroles/logging.viewer, or the role ID for acustom role, such asorganizations/{ORGANIZATION_ID}/roles/logging.viewer.

At most one of these can be specified:

--condition=[KEY=VALUE,…]

A condition to include in the binding. When the condition is explicitlyspecified asNone (--condition=None), a bindingwithout a condition is added. When the condition is specified and is notNone,--role cannot be a basic role. Basic roles areroles/editor,roles/owner, androles/viewer. For more on conditions, refer to the conditionsoverview guide:https://cloud.google.com/iam/docs/conditions-overview

When using the--condition flag, include the following key-valuepairs:

expression

(Required) Condition expression that evaluates to True or False. This uses asubset of Common Expression Language syntax.

If the condition expression includes a comma, use a different delimiter toseparate the key-value pairs. Specify the delimiter before listing the key-valuepairs. For example, to specify a colon (:) as the delimiter, do thefollowing:--condition=^:^title=TITLE:expression=EXPRESSION. Formore information, seehttps://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=PATH_TO_FILE

Path to a local JSON or YAML file that defines the condition. To see availablefields, see the help for--condition. Use a full or relative pathto a local file containing the value of condition.

Run$gcloud help for details.