gcloud access-context-manager supported-permissions describe

NAME

gcloud access-context-manager supported-permissions describe - describes which permissions in a provided role are supported by VPC Service Controls

SYNOPSIS

gcloud access-context-manager supported-permissions describe ROLE_ID [--organization=ORGANIZATION     | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG …]

DESCRIPTION

Describes which permissions in a provided role are supported by VPC Service Controls.

EXAMPLES

To describe which permissions VPC Service Controls supports for a provided role, run:

gcloud access-context-manager supported-permissions describe roles/example.role.name

This command prints out a list of all supported permissions in a tabular form:

ROLE NAME               SUPPORT STATUS SUPPORTED PERMISSIONS
roles/example.role.name SUPPORTED      example.permission.one
                                       example.permission.two

To describe which permissions VPC Service Controls supports for a custom role, run:

gcloud access-context-manager supported-permissions describe TestCustomRole --project=example-project

NOTE: If the provided role is a custom role, an organization or project must be specified.

This command prints out a list of all supported permissions in a tabular form:

ROLE NAME                                      SUPPORT STATUS SUPPORTED PERMISSIONS
projects/example-project/roles/TestCustomRole  SUPPORTED      example.permission.one

POSITIONAL ARGUMENTS

ROLE_ID

ID of the role to describe. Curated roles example: roles/viewer. Custom roles example: CustomRole. For custom roles, you must also specify the --organization or --project flag.

FLAGS

At most one of these can be specified:

--organization=ORGANIZATION

Organization of the role you want to describe.

--project=PROJECT_ID

Project of the role you want to describe.

The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be listed using gcloud config list --format='text(core.project)' and can be set using gcloud config set project PROJECTID.

--project and its fallback core/project property play two roles in the invocation: they specify both the project of the resource to operate on, and the project for API enablement checks, quota, and billing. To specify a different project for quota and billing, use the --billing-project flag or the billing/quota_project property.

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

These variants are also available:

gcloud alpha access-context-manager supported-permissions describe

gcloud beta access-context-manager supported-permissions describe