pipeline run migrate-cache

Migrates old pipeline run execution cache data that is created by pipeline runs to the new location. Identifiers of pipeline runs whose cache data is migrated are preserved in the output file. Cache data can be migrated to a mounted file system. To enable that option specify --assets-dir-path parameter.

Syntax

cpd-cli pipeline run migrate-cache \
--output-file=<output-file-location> \
[--asset-dir-path=<resource-reference>] \
[--cpd-scope=<cpd-scope>]
[--project-id=<project-id>] \
[--space-id=<space-identifier>]
[--verbose]

Options

Table 1: Command options
Option Description
--asset-dir-path Specify the path to the mounted assets directory. For example, /mnt/asset_file_api/projects/{project-id}/assets/.
Status
Optional.
Syntax
--asset-dir-path=<resource-reference>
Default value
No default.
--cpd-scope The IBM Software Hub space, project, or catalog scope. For example, cpd://default-context/spaces/7bccdda4-9752-4f37-868e-891de6c48135.
Status
Optional.
Syntax
--cpd-scope=<cpd-scope>
Default value
No default.
--output-file Specify the file path to where the identifiers of pipelines, jobs, and job runs are saved after the artifacts are deleted.
Status
Required.
Syntax
--output-file=<output-file-location>
Default value
No default.
Input type
string
--project-id Specify an IBM Software Hub project instance.
Status
Optional.
Syntax
--project-id=<project-id>
Default value
No default.
Input type
string
Valid values
A valid project identifier.
--space-id Specify a space identifier.
Status
Optional.
Syntax
--space-id=<space-identifier>
Default value
No default.
Input type
string
--verbose Display detailed processing information.
Status
Optional.
Syntax
--verbose
Default value
false
Input type
boolean
Valid values
False|True