Skip to main content
With plerion custom-checks, you can manage your own Rego checks and try a check against live assets before you save it.

Synopsis


Subcommands

list

get

create

Creates a check from a JSON definition. Pass - as the path to read from stdin.

update

Replaces the check in full with the definition in the file. Each update increments the check’s version.

delete

The check is removed immediately. Findings it produced are cleaned up in the background.

dry-run

Runs a check against the assets of one integration without saving findings. The check doesn’t need to be saved first, so you can test an edit before running update. Returns a dry run ID.

dry-run-status

Returns the status of a dry run: RUNNING, SUCCEEDED, FAILED, TIMED_OUT, or ABORTED. The table shows the status and the number of findings. Use --output json to see the preview findings once the run completes.

Check definition

create, update, and dry-run read the check as a JSON object.
The JSON from get --output json can be edited and sent straight back. The CLI drops the fields Plerion sets itself (such as version, createdAt, and updatedBy) before sending. For create and update it also drops customCheckId, which dry-run keeps to label its results.

Examples


Output columns

Dry run output columns