connection list-actions
List all supported connection actions.
Syntax
cpd-cli connection list-actions \
[--accept-language=<user-locale>] \
[--catalog-id=<catalog-id>] \
--connection-id=<connection-id> \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-config-location>] \
[--jmes-query=<jmespath-query>] \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
--profile=<cpd-configuration-profile-name> \
[--project-id=<cpd-project-id>] \
[--quiet] \
[--raw-output=true|false] \
[--space-id=<space-identifier>] \
[--verbose]
Arguments
The connection list-actions
command
has no arguments.
Options
Option | Description |
---|---|
--accept-language |
Specify the user's preferred locale identifier.
|
--catalog-id |
Specify either a catalog ID,
project ID, or space ID (specify only one).
|
--connection-id |
Specify the connection ID.
|
--context |
Specify whether assets are discovered for the purpose of 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).
|
|
Display command
help.
|
--jmes-query |
The Lucene
query.
|
--output |
Specify an output format.
Valid formats include json, yaml, or text (the default
format).
|
--output-file |
Specify a file path where all output is redirected.
|
--profile |
The profile-name from the Cloud
Pak for Data configuration.
|
--project-id |
Specify a Cloud Pak for Data project instance.
|
--quiet |
Suppress verbose messages.
|
--raw-output |
When set to true, single values in
JSON output mode are not surrounded by quotes.
|
--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 optionally add the
listed environment variables to the install variables script. For more information, see Best practice: Setting up install variables.
- Define the environment variables.
- Replace the following properties with your
data.
export CONNECTION_ID=<The connection identifier> export PROJECT_CPD_INSTANCE=<The Cloud Pak for Data project instance>
- List connection actions.
-
cpd-cli connection list-actions \ --connection-id=${CONNECTION_ID} \ --project-id=${PROJECT_CPD_INSTANCE}