gcloud_alpha_resource-manager_folders_remove-iam-policy-binding (1)
NAME
- gcloud alpha resource-manager folders remove-iam-policy-binding - remove IAM policy binding for a folder
SYNOPSIS
-
gcloud alpha resource-manager folders remove-iam-policy-binding FOLDER_ID --member=MEMBER --role=ROLE [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Removes a policy binding to the IAM policy of a folder, given a
POSITIONAL ARGUMENTS
-
- FOLDER_ID
-
ID for the folder to which you want to add a binding
REQUIRED FLAGS
-
- --member=MEMBER
-
The member 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.
Can also be one of the following special values:-
- ---
- allUsers - anyone who is on the internet, with or without a Google account.
- ---
- allAuthenticatedUsers - anyone who is authenticated with a Google account or a service account.
-
-
- --role=ROLE
-
The role to remove the member from.
GCLOUD WIDE FLAGS
These flags are available to all commands: --account, --configuration, --flags-file, --flatten, --format, --help, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details.
EXAMPLES
To remove an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' on folder with identifier '3589215982', run:
-
$ gcloud alpha resource-manager folders remove-iam-policy-binding \
3589215982 --member='user:test-user@gmail.com' \
--role='roles/editor'
To remove an IAM policy binding for the role of 'roles/editor' from all authenticated users on folder '3589215982', run:
-
$ gcloud alpha resource-manager folders remove-iam-policy-binding \
3589215982 --member='allAuthenticatedUsers' \
--role='roles/editor'
See cloud.google.com/iam/docs/managing-policies for details of policy role and member types.
NOTES
This command is currently in ALPHA and may change without notice. If this command fails with API permission errors despite specifying the right project, you will have to apply for early access and have your projects registered on the API whitelist to use it. To do so, contact Support at cloud.google.com/support