gcloud beta container fleet scopes add-iam-policy-binding - add IAM policy binding to a Fleet Scope

gcloud beta container fleet scopes add-iam-policy-bindingSCOPE--member=PRINCIPAL--role=ROLE[GCLOUD_WIDE_FLAG …]

gcloudbetacontainerfleetscopesadd-iam-policy-bindingmy-scope--member='user:test-user@gmail.com'--role='roles/gkehub.scopeUser'

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

Scope resource - The scope 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 argumentscope on the command line with a fullyspecified name;
• provide the argument--project on the command line;
• set the propertycore/project.

To set thelocation attribute:

• provide the argumentscope on the command line with a fullyspecified name;
• global is the only supported location.

This must be specified.

SCOPE

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

To set thescope attribute:

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

Run$gcloud help for details.