.TH "GCLOUD_ALPHA_COMPUTE_FIREWALL\-RULES_DESCRIBE" 1



.SH "NAME"
.HP
gcloud alpha compute firewall\-rules describe \- describe a Compute Engine firewall rule



.SH "SYNOPSIS"
.HP
\f5gcloud alpha compute firewall\-rules describe\fR \fINAME\fR [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR \fBgcloud alpha compute firewall\-rules describe\fR displays all
data associated with a Compute Engine firewall rule in a project.



.SH "EXAMPLES"

To describe a firewall rule, run:

.RS 2m
$ gcloud alpha compute firewall\-rules describe my\-firewall\-rule
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fINAME\fR

Name of the firewall rule to describe.


.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"

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:

.RS 2m
$ gcloud compute firewall\-rules describe
.RE

.RS 2m
$ gcloud beta compute firewall\-rules describe
.RE