connection list
List defined connections.
Syntax
cpd-cli connection list \
[--catalog-id=<catalog-id>] \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-scope>] \
[--entity-context=source|target|source,target] \
[--entity-datasource-type=<catalog-project-or-space-id>] \
[--entity-flags=<flag1,flag2,...>] \
[--entity-name=<asset-type-name>] \
[--entity-properties=<connection-properties>] \
[--inject-token=true|false] \
[--jmes-query=<jmespath-query>] \
[--limit=<resource-limit>] \
[--metadata-creator=<connection-creator>] \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
--profile=<cpd-profile-name> \
[--project-id=<cpd-project-id>] \
[--quiet] \
[--raw-output=true|false] \
[--sort=<field-sort-order>] \
[--space-id=<space-identifier>] \
[--start=<start-token>] \
[--verbose]
Arguments
The connection list
command has no
arguments.
Options
Table 1: Command options
Option | Description |
---|---|
--catalog-id |
Specify either a catalog ID,
project ID, or space ID (specify one only).
|
--context |
Specify whether assets
are discovered for reading (source) or writing (target). 'source' is the default when
no value is
specified.
|
--cpd-config |
The Cloud Pak for Data
configuration location. For example,
$HOME/.cpd-cli/config.
|
--cpd-scope |
The Cloud Pak for Data space, project, or catalog scope. For example, cpd://default-context/spaces/7bccdda4-9752-4f37-868e-891de6c48135.
|
--entity-context |
Specify the connection context.
Available options are "source", "target",
or
"source,target".
|
--entity-datasource-type |
Specify the data source
connection
type.
|
--entity-flags |
Specify a comma-separated list of
flags that must be present for the connection to be included in the list. Only connections with no
flags are returned when the option is not specified.
|
--entity-name |
Specify a connection
name.
|
--entity-properties |
Specify the connection properties
that must match so that the connection is included in the
list.
|
|
Display command
help.
|
--inject-token |
Indicate whether the cluster
username and access token should be injected into the connection properties. The access token is not
revealed
unintentionally together with connection
properties.
|
--jmes-query |
The Lucene
query.
|
--limit |
Specify the total number of
resources.
|
--metadata-creator |
Specify the connection
creator.
|
--output |
Specify an output
format.
|
--output-file |
Specify a file path where all
output is redirected.
|
--profile |
The name of the profile that you
created to store information about an instance of Cloud Pak for Data and your credentials for the
instance.
|
--project-id |
Specify a Cloud Pak for Data
project instance.
|
--quiet |
Suppress verbose
messages.
|
--raw-output |
When set to true, single values
are not surrounded by quotation marks in
JSON output
mode.
|
--sort |
The field to
sort the
results on, including whether to sort ascending (+) or descending (-). For example,
'--sort=-metadata.create_time'.
|
--space-id |
Specify a space
identifier.
|
--start |
Specify the token that represents
the first resource.
|
--verbose |
Logs include more detailed
messages.
|
Examples
Note: The following examples use environment variables. Use a script to create
environment variables with the correct values for your environment. You can add the listed
environment variables to the installation variables script. For more information, see Setting up installation environment variables.
- List connections for the specified Cloud Pak for Data project.
-
cpd-cli connection list \ --project-id=${PROJECT_CPD_INST_OPERANDS}