Usage
gable lineage upload [OPTIONS]
Options
| Option | Type | Required | Default | Description | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
--project-root | path | The root directory of the project that will be analyzed. | |||||||||
--results-file | path | Upload one legacy results file. No sibling files are discovered. | |||||||||
--strands-file | path | Explicit path to Prime’s strands.json. Requires —metadata-file and —code-paths-file. | |||||||||
--metadata-file | path | Explicit path to Prime’s strand-metadata.json. Requires —strands-file and —code-paths-file. | |||||||||
--code-paths-file | path | Explicit path to Prime’s code-paths.json. Requires —strands-file and —metadata-file. | |||||||||
--analysis-coverage-file | path | Explicit section coverage for referenced artifacts. Requires —run-id and all three artifact files. | |||||||||
--namespace | text | INTERNAL: select the namespace you want lineage results to be associated with. | |||||||||
--external-component-id | text | External component id. | |||||||||
--payload-type | CODE | DATA_STORE | EDGE | CODE_STRANDS | DATA_COMPONENTS | CODE_DATA_EDGES | COMPLIANCE | AI_AUGMENTATION | Route a results file without parsing its JSON envelope in the CLI. Must be supplied together with —run-id. | ||
--run-id | uuid | Resume an upload with a previously printed UUIDv7. If omitted, a fresh run ID is generated. | |||||||||
--component-name | text | Name for the CODE component this upload creates. By default the backend names the component after the repository; pass a name when one repository is uploaded as several components (for example one per agent-graph node), together with a distinct —external-component-id per component. |
Example
gable lineage upload --project-root . --namespace dev --results-file results.json
gable lineage upload --project-root . --namespace dev --strands-file strands.json
--metadata-file strand-metadata.json --code-paths-file code-paths.json