
.TH "GCLOUD_ACCESS\-CONTEXT\-MANAGER_PERIMETERS_DRY\-RUN_LIST" 1



.SH "NAME"
.HP
gcloud access\-context\-manager perimeters dry\-run list \- list the effective dry\-run configuration across all Service Perimeters



.SH "SYNOPSIS"
.HP
\f5gcloud access\-context\-manager perimeters dry\-run list\fR [\fB\-\-policy\fR=\fIpolicy\fR] [\fB\-\-filter\fR=\fIEXPRESSION\fR] [\fB\-\-limit\fR=\fILIMIT\fR] [\fB\-\-page\-size\fR=\fIPAGE_SIZE\fR] [\fB\-\-sort\-by\fR=[\fIFIELD\fR,...]] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

By default, only the Service Perimeter name, title, type and the dry\-run mode
configuration (as \f5spec\fR) is displayed.

Note: For Service Perimeters without an explicit dry\-run mode configuration,
the enforcement mode configuration is used as the dry\-run mode configuration,
resulting in no audit logs being generated.



.SH "EXAMPLES"

To list the dry\-run mode configuration across all Service Perimeter:

.RS 2m
$ gcloud access\-context\-manager perimeters dry\-run list
.RE

Output:

.RS 2m
name: perimeter_1*
spec:
  resources:
  \- projects/123
  \- projects/456
  restrictedServices:
  \- storage.googleapis.com
title: Perimeter 1
\-\-\-
name: perimeter_2
spec:
  resources:
  \- projects/789
  restrictedServices:
  \- bigquery.googleapis.com
  vpcAccessibleServices:
    allowedServices:
    \- bigquery.googleapis.com
    enableRestriction: true
title: Perimeter 2
.RE



.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-policy\fR=\fIpolicy\fR

Policy resource \- The access policy you want to list the effective dry\-run
configuration for. This represents a Cloud resource.


.RE
.sp

.SH "LIST COMMAND FLAGS"

.RS 2m
.TP 2m
\fB\-\-filter\fR=\fIEXPRESSION\fR

Apply a Boolean filter \fIEXPRESSION\fR to each resource item to be listed. If
the expression evaluates \f5True\fR, then that item is listed. For more details
and examples of filter expressions, run $ gcloud topic filters. This flag
interacts with other flags that are applied in this order: \fB\-\-flatten\fR,
\fB\-\-sort\-by\fR, \fB\-\-filter\fR, \fB\-\-limit\fR.

.TP 2m
\fB\-\-limit\fR=\fILIMIT\fR

Maximum number of resources to list. The default is \fBunlimited\fR. This flag
interacts with other flags that are applied in this order: \fB\-\-flatten\fR,
\fB\-\-sort\-by\fR, \fB\-\-filter\fR, \fB\-\-limit\fR.

.TP 2m
\fB\-\-page\-size\fR=\fIPAGE_SIZE\fR

Some services group resource list output into pages. This flag specifies the
maximum number of resources per page. The default is determined by the service
if it supports paging, otherwise it is \fBunlimited\fR (no paging). Paging may
be applied before or after \fB\-\-filter\fR and \fB\-\-limit\fR depending on the
service.

.TP 2m
\fB\-\-sort\-by\fR=[\fIFIELD\fR,...]

Comma\-separated list of resource field key names to sort by. The default order
is ascending. Prefix a field with ``~'' for descending order on that field. This
flag interacts with other flags that are applied in this order:
\fB\-\-flatten\fR, \fB\-\-sort\-by\fR, \fB\-\-filter\fR, \fB\-\-limit\fR.


.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "NOTES"

These variants are also available:

.RS 2m
$ gcloud alpha access\-context\-manager perimeters dry\-run list
.RE

.RS 2m
$ gcloud beta access\-context\-manager perimeters dry\-run list
.RE


