gcloud beta container fleet scopes add-app-operator-binding

NAME
gcloud beta container fleet scopes add-app-operator-binding - add project-level and fleet scope-level IAM bindings and create a fleet scope RBAC role binding for an app operator principal
SYNOPSIS
gcloud beta container fleet scopes add-app-operator-binding SCOPE (--custom-role=CUSTOM_ROLE     | --role=ROLE) (--group=GROUP     | --user=USER) [--labels=[KEY=VALUE,…]] [GCLOUD_WIDE_FLAG]
DESCRIPTION
(BETA) One binding consists of an app operator principal (user/group) and a role (view/edit/admin or a custom role).

This command sets up the different permissions required for an app operator, including usage of fleet scopes, connect gateway, logging, and metrics. The authoritative list for adding the permissions is the existing RBAC role bindings under the specified scope.

This command can fail for the following reasons:
EXAMPLES
The following command:
gcloud beta container fleet scopes add-app-operator-binding SCOPE --role=view --group=people@google.com --project=PROJECT_ID

---

The following command:

gcloud beta container fleet scopes add-app-operator-binding SCOPE --role=edit --user=person@google.com --project=PROJECT_ID

---

The following command:

gcloud beta container fleet scopes add-app-operator-binding SCOPE --role=admin --user=person@google.com --project=PROJECT_ID

---

The following command:

gcloud beta container fleet scopes add-app-operator-binding SCOPE --custom-role=my-custom-role --user=person@google.com --project=PROJECT_ID
For any tailored IAM permissions required when using a custom role, the user or group can separately be granted additional IAM permissions on the project.
POSITIONAL ARGUMENTS
Scope resource - The group of arguments defining the Fleet Scope. 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:

To set the location attribute:

This must be specified.
SCOPE
ID of the scope or fully qualified identifier for the scope. To set the scope attribute:
REQUIRED FLAGS
Exactly one of these must be specified:
--custom-role=CUSTOM_ROLE
Custom role to assign to principal.
--role=ROLE
Predefined role to assign to principal (admin, edit, view). ROLE must be one of: admin, edit, view.
Exactly one of these must be specified:
--group=GROUP
Group for the role binding.
--user=USER
User for the role binding.
OPTIONAL FLAGS
--labels=[KEY=VALUE,…]
List of label KEY=VALUE pairs to add. Keys must start with a lowercase character and contain only hyphens (-), underscores (_), lowercase characters, and numbers. Values must contain only hyphens (-), underscores (_), lowercase characters, and numbers.
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.

NOTES
This command is currently in beta and might change without notice. This variant is also available:
gcloud alpha container fleet scopes add-app-operator-binding