Get Evidence CLI
The Get Evidence command exports a list of all evidence associated with an artifact or a Release Bundle v2.
Note
You can also get evidence using a GraphQL API command. For more information, see Get Evidence.
Syntax
JFrog CLI uses the following syntax for getting evidence:
Artifact Evidence
jf evd get --subject-repo-path <target-path> --output <file-name>Release Bundle v2 Evidence
jf evd get --release-bundle <name> --release-bundle-version <version-number> --output <file-name>Note
For sample commands, click here.
Command Parameters
| Parameter | Required/Optional | Type | Description |
|---|---|---|---|
--output | required | string | Name of the file to which evidence is exported. |
--include-predicate | optional | string | Flag that determines whether the predicate is included in the exported file. By default, the predicate is not included. |
--format | optional | string | Enables extended output. Supported formats: json, jsonl |
Tip
We recommend not to include the predicate if the evidence list is large, as the predicate will have a significant impact on file size.
Artifact Command Parameters
Parameter | Required/Optional | Type | Description |
|---|---|---|---|
| required | string | The path of the evidence target. Each evidence file must contain a single subject and must include the path. Artifacts located in local repositories that are aggregated inside virtual repositories are supported. |
Release Bundle v2 Command Parameters
| Parameter | Required/Optional | Type | Description |
|---|---|---|---|
--release-bundle | required | string | The Release Bundle name. |
--release-bundle-version | required | string | The Release Bundle version. |
--artifacts-limit | optional | integer | The maximum number of artifacts in the Release Bundle to include in the evidence list. The default is 1000 artifacts. |
Updated about 2 months ago