.TH "GCLOUD_DATASTREAM_CONNECTION\-PROFILES_DISCOVER" 1



.SH "NAME"
.HP
gcloud datastream connection\-profiles discover \- discover a Datastream connection profile



.SH "SYNOPSIS"
.HP
\f5gcloud datastream connection\-profiles discover\fR \fB\-\-location\fR=\fILOCATION\fR (\fB\-\-connection\-profile\-name\fR=\fICONNECTION_PROFILE_NAME\fR\ |\ \fB\-\-connection\-profile\-object\-file\fR=\fICONNECTION_PROFILE_OBJECT_FILE\fR) [\fB\-\-full\-hierarchy\fR\ |\ \fB\-\-hierarchy\-depth\fR=\fIHIERARCHY_DEPTH\fR] [\fB\-\-mysql\-rdbms\-file\fR=\fIMYSQL_RDBMS_FILE\fR\ |\ \fB\-\-oracle\-rdbms\-file\fR=\fIORACLE_RDBMS_FILE\fR\ |\ \fB\-\-postgresql\-rdbms\-file\fR=\fIPOSTGRESQL_RDBMS_FILE\fR\ |\ \fB\-\-sqlserver\-rdbms\-file\fR=\fISQLSERVER_RDBMS_FILE\fR] [\fB\-\-recursive\fR\ |\ \fB\-\-recursive\-depth\fR=\fIRECURSIVE_DEPTH\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Discover data objects accessible from a Datastream connection profile



.SH "EXAMPLES"

To discover an existing connection profile:

.RS 2m
$ gcloud datastream connection\-profiles discover \e
  CONNECTION_PROFILE \-\-location=us\-central1 \e
  \-\-connection\-profile\-name=some\-cp \-\-recursive=true
.RE

To discover a non\-existing connection profile:

.RS 2m
$ gcloud datastream connection\-profiles discover \e
  CONNECTION_PROFILE \-\-location=us\-central1 \e
  \-\-connection\-profile\-object\-file=path/to/yaml/or/json/file
.RE



.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m

Location resource \- The location you want to list the connection profiles for.
This represents a Cloud resource. (NOTE) Some attributes are not given arguments
in this group but can be set in other ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5\-\-location\fR on the command line with a fully
specified name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fB\-\-location\fR=\fILOCATION\fR

ID of the location or fully qualified identifier for the location.

To set the \f5location\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5\-\-location\fR on the command line.
.RE
.sp

.RE
.sp
.TP 2m

Exactly one of these must be specified:


.RS 2m
.TP 2m

Connection profile resource \- Resource ID of the connection profile. This
represents a Cloud resource. (NOTE) Some attributes are not given arguments in
this group but can be set in other ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5\-\-connection\-profile\-name\fR on the command line
with a fully specified name;
.IP "\(bu" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(bu" 2m
set the property \f5core/project\fR.
.RE
.sp

To set the \f5location\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5\-\-connection\-profile\-name\fR on the command line
with a fully specified name;
.IP "\(bu" 2m
provide the argument \f5\-\-location\fR on the command line.
.RE
.sp


.RS 2m
.TP 2m
\fB\-\-connection\-profile\-name\fR=\fICONNECTION_PROFILE_NAME\fR

ID of the connection_profile or fully qualified identifier for the
connection_profile.

To set the \f5connection_profile\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5\-\-connection\-profile\-name\fR on the command line.
.RE
.sp

.RE
.sp
.TP 2m
\fB\-\-connection\-profile\-object\-file\fR=\fICONNECTION_PROFILE_OBJECT_FILE\fR

Path to a YAML (or JSON) file containing the configuration for a connection
profile object. If you pass \- as the value of the flag the file content will be
read from stdin.


.RE
.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-full\-hierarchy\fR

Whether to retrieve the full hierarchy of data objects (TRUE) or only the
current level (FALSE).

.TP 2m
\fB\-\-hierarchy\-depth\fR=\fIHIERARCHY_DEPTH\fR

The number of hierarchy levels below the current level to be retrieved.

.RE
.sp
.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-mysql\-rdbms\-file\fR=\fIMYSQL_RDBMS_FILE\fR

Path to a YAML (or JSON) file containing the MySQL RDBMS to enrich with child
data objects and metadata. If you pass \- as the value of the flag the file
content will be read from stdin.

.TP 2m
\fB\-\-oracle\-rdbms\-file\fR=\fIORACLE_RDBMS_FILE\fR

Path to a YAML (or JSON) file containing the Oracle RDBMS to enrich with child
data objects and metadata. If you pass \- as the value of the flag the file
content will be read from stdin.

.TP 2m
\fB\-\-postgresql\-rdbms\-file\fR=\fIPOSTGRESQL_RDBMS_FILE\fR

Path to a YAML (or JSON) file containing the PostgreSQL RDBMS to enrich with
child data objects and metadata. If you pass \- as the value of the flag the
file content will be read from stdin.

.TP 2m
\fB\-\-sqlserver\-rdbms\-file\fR=\fISQLSERVER_RDBMS_FILE\fR

Path to a YAML (or JSON) file containing the SQL Server RDBMS to enrich with
child data objects and metadata. If you pass \- as the value of the flag the
file content will be read from stdin.

.RE
.sp
.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-recursive\fR

(DEPRECATED) Whether to retrieve the full hierarchy of data objects (TRUE) or
only the current level (FALSE).

The \-\-recursive option is deprecated; use \f5\-\-full\-hierarchy\fR instead.

.TP 2m
\fB\-\-recursive\-depth\fR=\fIRECURSIVE_DEPTH\fR

(DEPRECATED) The number of hierarchy levels below the current level to be
retrieved.

The \-\-recursive\-depth option is deprecated; use \f5\-\-hierarchy\-depth\fR
instead.


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

.RS 2m
$ gcloud beta datastream connection\-profiles discover
.RE