gcloud alpha compute snapshots add-iam-policy-binding - add IAM policy binding to a Compute Engine snapshot

gcloud alpha compute snapshots add-iam-policy-bindingSNAPSHOT_NAME--member=PRINCIPAL--role=ROLE[--condition=[KEY=VALUE,…]    |--condition-from-file=PATH_TO_FILE][GCLOUD_WIDE_FLAG …]

gcloudalphacomputesnapshotsadd-iam-policy-bindingmy-snapshot--member='user:test-user@gmail.com'--role='roles/compute.securityAdmin'

To add an IAM policy binding which expires at the end of the year 2018 for therole of 'roles/compute.securityAdmin' and the user 'test-user@gmail.com' withsnapshot 'my-snapshot', run:

gcloudalphacomputesnapshotsadd-iam-policy-bindingmy-snapshot--member='user:test-user@gmail.com'--role='roles/compute.securityAdmin'--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.

Snapshot resource - The snapshot for which to add IAM policy binding to. Thisrepresents a Cloud resource. (NOTE) Some attributes are not given arguments inthis group but can be set in other ways.

To set theproject attribute:

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

This must be specified.

SNAPSHOT_NAME

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

To set thesnapshot_name attribute:

• provide the argumentsnapshot_name 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.

--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.