.TH "GCLOUD_ALPHA_DATAFLOW_JOBS_EXPORT\-STEPS" 1



.SH "NAME"
.HP
gcloud alpha dataflow jobs export\-steps \- exports information about the steps for the given job



.SH "SYNOPSIS"
.HP
\f5gcloud alpha dataflow jobs export\-steps\fR \fIJOB_ID\fR [\fB\-\-region\fR=\fIREGION_ID\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR The only currently supported format is to a GraphViz dot file.



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fIJOB_ID\fR

Job ID to operate on.


.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-region\fR=\fIREGION_ID\fR

Region ID of the job's regional endpoint. Defaults to 'us\-central1'.


.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. This variant is also available:

.RS 2m
$ gcloud beta dataflow jobs export\-steps
.RE