When to use
- Download a deployed use case from the platform
- Restore a previously deployed use case to local files
- Inspect what documents are stored for a project
- Pull the latest deployed version locally
Prerequisites
codikaCLI installed and authenticated- Project ID of the deployed use case
Resolving the project ID
The CLI requires a project ID, not a folder path. If the user provides a use case folder path instead, readproject.json from that folder to get the projectId:
Command
Arguments
| Argument | Description |
|---|---|
<projectId> | Project ID of the deployed use case (from project.json) |
[outputPath] | Output directory (defaults to ./<projectId>) |
Options
| Option | Description | Default |
|---|---|---|
--target-version <X.Y> | Fetch specific version | Latest |
--with-data-ingestion | Include data ingestion workflow | true |
--no-data-ingestion | Exclude data ingestion workflow | — |
--di-version <version> | Data ingestion version in X.Y format | Latest |
--list | List documents without downloading | — |
--api-url <url> | Override API URL | — |
--api-key <key> | Override API key | — |
--profile <name> | Use a specific profile instead of the active one | — |
--json | JSON output | — |
Behavior
Download mode (default):- Fetches metadata documents from the API
- Decodes file content
- Writes files to the output directory
--list):
- Fetches document listing only
- Displays file paths, sizes, and content types
- Does not download any files
Examples
Output
Download mode
List mode
Exit codes
| Code | Meaning |
|---|---|
0 | Success |
1 | API error or project not found |