datastage subflow create
Create a DataStage subflow in a specified project or catalog (either project_id or catalog_id must be set).
Syntax
cpd-cli datastage subflow create \
[--catalog-id=<catalog-id>] \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-config-location>] \
[--jmes-query=<jmespath-query>] \
--name=<datastage-subflow-name> \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
[--pipeline-flow=<pipeline-flow-to-store>] \
--profile=<cpd-configuration-profile-name> \
[--project-id=<cpd-project-id>] \
[--quiet] \
[--raw-output=true|false] \
[--space-id=<space-identifier>] \
[--verbose]
Arguments
The datastage subflow create
command has no arguments.
Options
Option | Description |
---|---|
--catalog-id |
Specify either a catalog ID,
project ID, or space ID (specify only one).
|
--context |
Specify the configuration context
name.
|
--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.
|
--name |
Specify the DataStage subflow
name upon which to filter results.
|
--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.
|
--pipeline-flow |
Specify the pipeline flow to store.
|
--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.
|