gcloud alpha compute backend-services remove-iam-policy-binding

NAME
gcloud alpha compute backend-services remove-iam-policy-binding - remove an IAM policy binding from a Compute Engine backend service
SYNOPSIS
gcloud alpha compute backend-services remove-iam-policy-binding BACKEND_SERVICE_NAME --member=PRINCIPAL --role=ROLE [--global     | --region=REGION] [GCLOUD_WIDE_FLAG]
DESCRIPTION
(ALPHA) Remove an IAM policy binding from a Compute Engine backend service.
EXAMPLES
To remove an IAM policy binding for the role of 'roles/compute.loadBalancerServiceUser' for the user 'test-user@gmail.com' with backend service 'my-backend-service' and region 'REGION', run:
gcloud alpha compute backend-services remove-iam-policy-binding my-backend-service --region=REGION --member='user:test-user@gmail.com' --role='roles/compute.loadBalancerServiceUser'
gcloud alpha compute backend-services remove-iam-policy-binding my-backend-service --global --member='user:test-user@gmail.com' --role='roles/compute.loadBalancerServiceUser'

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

POSITIONAL ARGUMENTS
BACKEND_SERVICE_NAME
Name of the backend service to operate on.
REQUIRED FLAGS
--member=PRINCIPAL
The principal to remove the binding for. Should be of the form user|group|serviceAccount:email or domain:domain.

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

Deleted principals have an additional deleted: prefix and a ?uid=UID suffix, where UID is a unique identifier for the principal. Example: deleted:user:test-user@gmail.com?uid=123456789012345678901.

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
The role to remove the principal from.
OPTIONAL FLAGS
At most one of these can be specified:
--global
If set, the backend service is global.
--region=REGION
Region of the backend service to operate on. Overrides the default compute/region property value for this command invocation.
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 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 compute backend-services remove-iam-policy-binding
gcloud beta compute backend-services remove-iam-policy-binding