export-import schedule-export create

Schedule recurring export jobs. The export job will create a file that contains the assets that you want to export.

Syntax

cpd-cli export-import schedule-export create <cpd-export-schedule-name> \
[--arch=<system-cpu-architecture>] \
[--backoff-limit] \
[--cpdconfig=<cpd-configuration-location>] \
[--component=<cpd-export-component>] \
[--instance-name=<service-instance-name>] \
[--log-level=info|debug|warn|error|panic|trace] \
[--namespace=<namespace-name>] \
--profile=<cpd-profile-name> \
[--schedule=<cron-job-schedule>] \
[--service-type=<cpd-service-type>] \
[--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

Table 1: Command options
Option Description
--arch The type of hardware the cluster runs on.
Status
Optional.
Syntax
--arch=${CPU_ARCH}
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.
--backoff-limit The number of times to retry an export or import job before the job fails. Setting --backoff-limit=0 disables the retry.
Status
Optional.
Syntax
--backoff-limit=<backoff-limit>
Default value
1
Valid values
The backoff-limit can be any integer value equal to or greater than 0.
A backoff-limit of 0 disables retry.
--cpdconfig The IBM Software Hub
 configuration location. For example, $HOME/.cpd-cli/config.
Status
Optional.
Syntax
--cpdconfig=<cpd-configuration-location>
Default value
$HOME/.cpd-cli/config
Valid values
A valid IBM® Software Hub configuration location.

--component

-c

 The component that you want to export assets from.
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=<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|trace
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.
trace
Trace messages are written to the log.
--namespace

-n

 The namespace name in which the utility should operate.
Status
Optional.
Syntax
--namespace=<namespace-name>
Valid values
A valid project (namespace) name. Use ${PROJECT_CPD_INST_OPERANDS}.
--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.
Status
Required.
Syntax
--profile=<cpd-profile-name>
Default value
No default.
Valid values

The name of the profile that you created.
--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 instance type.
Status
Optional.
Syntax
--service-type=<cpd-service-type>
Default value
No default.
Valid values
Any valid Cloud Pak for Data service type. For example, 'dv'. Use the 'cpd-cli service-instance list' command to find the 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.

It is strongly recommended that you use a script to create environment variables with the correct values for your environment. For more information, see Setting up installation environment variables.

Create a schedule export from Cloud Pak for Data in the ${PROJECT_CPD_INST_OPERANDS} 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_INST_OPERANDS}