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-scope>] \
[--jmes-query=<jmespath-query>] \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
--profile=<cpd-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 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 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.
|
--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.
|
--space-id |
Specify a space
identifier.
|
--verbose |
Logs include more detailed
messages.
|
Table 1: Command options
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 Best practice: Setting up installation environment variables.
- Define the environment variables.
- Replace the following properties with your
data.
export CONNECTION_ID=<The connection identifier>
- List connection actions.
-
cpd-cli connection list-actions \ --connection-id=${CONNECTION_ID} \ --project-id=${PROJECT_CPD_INST_OPERANDS}