gcloud beta access-context-manager lookup-configured-perimeter

INFORMATION
gcloud beta access-context-manager lookup-configured-perimeter is supported in universe domain universe; however, some of the values used in the help text may not be available. Command examples may not work as-is and may requires changes before execution.
NAME
gcloud beta access-context-manager lookup-configured-perimeter - look up the configured VPC Service Controls service perimeter for a resource
SYNOPSIS
gcloud beta access-context-manager lookup-configured-perimeter --resource=RESOURCE [GCLOUD_WIDE_FLAG …]
DESCRIPTION
(BETA) Looks up the configured VPC Service Controls service perimeter (both enforced and dry-run) that applies to the specified project or folder based on resource hierarchy ancestry.
EXAMPLES
To look up the configured perimeter for a project with number 1234567890: 
gcloud beta access-context-manager lookup-configured-perimeter --resource=projects/1234567890

To look up the configured perimeter for a folder with number 9876543210: 

gcloud beta access-context-manager lookup-configured-perimeter --resource=folders/9876543210
REQUIRED FLAGS
--resource=RESOURCE
The resource to look up effective service perimeters for. Format: projects/{project_number} or folders/{folder_number}.
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. These variants are also available: 
gcloud access-context-manager lookup-configured-perimeter
 
gcloud alpha access-context-manager lookup-configured-perimeter