gcloud alpha container hub scopes add-iam-policy-binding

NAME

gcloud alpha container hub scopes add-iam-policy-binding - add IAM policy binding to a Fleet Scope

SYNOPSIS

gcloud alpha container hub scopes add-iam-policy-binding SCOPE --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG …]

DESCRIPTION

(ALPHA) Add an IAM policy binding to the IAM policy of a Fleet Scope. One binding consists of a member, and a role.

EXAMPLES

To add an IAM policy binding for the role of 'roles/gkehub.scopeUser' for the user '[e-mail]' with scope 'my-scope', run:

gcloud alpha container hub scopes add-iam-policy-binding my-scope --member='user:[e-mail]' --role='roles/gkehub.scopeUser'

See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types.

POSITIONAL ARGUMENTS

Scope resource - The scope for which to add IAM policy binding to. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways.

To set the project attribute:

• provide the argument scope on the command line with a fully specified name;
• provide the argument --project on the command line;
• set the property core/project.

To set the location attribute:

• provide the argument scope on the command line with a fully specified 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 the scope attribute:

• provide the argument scope on the command line.

REQUIRED FLAGS

--member=PRINCIPAL

The principal to add the binding for. Should be of the form user|group|serviceAccount:email or domain:domain.

Examples: user:[e-mail], group:[e-mail], serviceAccount:[e-mail], or domain:example.domain.com.

Some resources also accept the following special values:

• allUsers - Special identifier that represents anyone who is on the internet, with or without a Google account.
• allAuthenticatedUsers - Special identifier that represents anyone who 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 a predefined role, such as roles/logging.viewer, or the role ID for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer.

GCLOUD WIDE FLAGS

These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.

Run $ gcloud help for details.

API REFERENCE

This command uses the gkehub/v1alpha API. The full documentation for this API can be found at: https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster

NOTES

This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. These variants are also available:

gcloud container hub scopes add-iam-policy-binding

gcloud beta container hub scopes add-iam-policy-binding