export-import schedule-export create

Create an IBM® Cloud Pak for Data schedule export.

Syntax

cpd-cli export-import schedule-export create <cpd-export-schedule-name> \
[--arch=<system-cpu-architecture>] \
[--cpdconfig=<cpd-configuration-location>] \
[--component=<cpd-export-component>] \
[--instance-name=<cpd-service-instance-name>] \
[--log-level=info|debug|warn|error|panic] \
[--namespace=<namespace-name>] \
--profile=<cpd-configuration-profile-name> \
[--schedule=<cron-job-schedule>] \
[--service-type=<cpd-service-name>] \
[--values=<yaml-file-name1,yaml-file-name2,...>] \
[--verbose]

Arguments

Table 1: Command arguments
Argument Description
<cpd-export-schedule-name> The name of the scheduled export to create.

Options

Option Description
--arch Provide the system architecture.
Status
Optional.
Syntax
--arch=<system-cpu-architecture>
Default value
x86_64
Valid values
x86_64
The 64-bit version of the x86 instruction set architecture.
ppc64le
The little-endian variant of the PowerPC 64-bit architecture.
--cpdconfig The Cloud Pak for Data configuration location.
Status
Optional.
Syntax
--cpdconfig=<cpd-configuration-location>
Default value
$HOME/.cpd-cli/config
Valid values
A valid Cloud Pak for Data configuration location.

--component

-c

 The Cloud Pak for Data component for export.
Status
Optional.
Syntax
--component=<cpd-export-component>
Default value
No default.
Valid values
A valid Cloud Pak for Data component name.

--help

-h

 Display command help.
Status
Optional.
Syntax
--help
Default value
No default.
Valid values
Not applicable.
--instance-name Specify the Cloud Pak for Data service instance name.
Status
Optional.
Syntax
--instance-name=<cpd-service-instance-name>
Default value
No default.
Valid values
A Cloud Pak for Data service instance name.
--log-level The command log level.
Status
Optional.
Syntax
--log-level=info|debug|warn|error|panic
Default value
info
Valid values
debug
Debug messages are written to the log.
error
Error messages are written to the log.
info
Informative messages are written to the log.
panic
Panic messages are written to the log.
warn
Warning messages are written to the log.
--namespace

-n

 The namespace name in which the utility should operate.
Status
Optional.
Syntax
--namespace=<namespace-name>
Default value
${PROJECT_CPD_INSTANCE}
Valid values
A valid project (namespace) name.
--profile The profile-name from the Cloud Pak for Data configuration.
Status
Required.
Syntax
--profile=<cpd-configuration-profile-name>
Default value
default
Valid values
Any valid profile name from the Cloud Pak for Data configuration.
--schedule Specify a job schedule in the Cron format.
Status
Optional.
Syntax
--schedule=<cron-job-schedule>
Default value
No default.
Valid values
A valid Cron job schedule name.
--service-type The Cloud Pak for Data service name.
Status
Optional.
Syntax
--service-type=<cpd-service-name>
Default value
No default.
Valid values
Any valid OpenShift® Container Platform service type.

--values

-r

 Specify values in one or more YAML files.
Status
Optional.
Syntax
--values=<yaml-file-name1,yaml-file-name2,...>
Default value
No default.
Valid values
One or more YAML file names.
--verbose Logs include more detailed messages.
Status
Optional.
Syntax
--verbose
Default value
No default.
Valid values
Not applicable.

Examples

Note: The following examples use the recommended installation environment variables.

Use a script to create environment variables with the correct values for your environment. For more information, see Best practice: Setting up install variables.

Create a schedule export from Cloud Pak for Data in the ${PROJECT_CPD_INSTANCE} namespace.
cpd-cli export-import schedule-export create <cpd-export-schedule-name> \
--component=<cpd-export-component> \
--values=<yaml-file-name.yaml> \
--log-level=error \
--namespace=${PROJECT_CPD_INSTANCE}