connection get
Retrieve details for a specific connection definition.
Syntax
cpd-cli connection get \
--connection-id=<connection-id> \
--profile=<cpd-profile-name> \
[--catalog-id=<catalog-id>] \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-scope>] \
[--entity-product=<string1,string2,...>] \
[--inject-token=true|false] \
[--jmes-query=<jmespath-query>] \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
[--project-id=<project-id>] \
[--quiet] \
[--raw-output=true|false] \
[--space-id=<space-identifier>] \
[--verbose]
Arguments
The connection get 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).
|
--connection-id |
Specify the connection
ID.
|
--context |
Specify whether assets
are discovered for reading (source) or writing (target). 'source' is the default when
no value is
specified.
|
--cpd-config |
The IBM Software Hub
configuration location. For example,
$HOME/.cpd-cli/config.
|
--cpd-scope |
The IBM Software Hub space,
project, or catalog scope. For example,
cpd://default-context/spaces/7bccdda4-9752-4f37-868e-891de6c48135.
|
--detail |
When the option is set to 'true',
additional asset-specific details are returned. When the option is set to 'false' specified, the
details are
not returned.
|
--entity-product |
Specify the product that the
data
source type must support to be returned. The available products are 'catalog',
'cpd',
'datastage', 'dv', 'igc', 'mdi', 'ml', and 'studio'. Filtering is not applied unless the
entity product is specified. Use a comma-separated string to specify multiple environments. For
example,
--entity-product=catalog,studio.
|
|
|
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 |
Provide a JMESPath query to
customize the output.
|
--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 an IBM Software Hub
project instance.
|
--quiet |
Suppress verbose
messages.
|
--raw-output |
When set to true, single values
are not surrounded by quotation marks in
JSON output
mode.
|
--space-id |
Specify a space
identifier.
|
--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.
- Define the environment variables.
-
export CONNECTION_ID=<The connection identifier> - Retrieve a connection.
-
cpd-cli connection get \ --connection-id=${CONNECTION_ID} \ --project-id=zen