Work with patchy security findings from the terminal
patchy lists, inspects, reviews and acts on the custom resources that carry the patchy pipeline's state machine.
It talks to the Kubernetes API with your own kubeconfig — never through a
controller or the status page — so what you can do is what your RBAC allows.
Run patchy can-i to see your grants.
-A, --all-namespaces work across every namespace
--context string kubeconfig context to use
-h, --help help for patchy
--kubeconfig string path to the kubeconfig file
-n, --namespace string namespace to work in (default: the context's)
--no-color disable colour and styling
-o, --output string output format: table, wide, json, yaml, name, or markdown (default "table")
--request-timeout duration timeout for a single API call (default 30s)
-v, --verbose log what the CLI is doing to stderr
- patchy approve - Approve a finding, releasing a hold or reviving a handed-off finding
- patchy backfill - Backfill an integration's pre-existing open alerts into findings
- patchy browse - Browse to a resource's page in a browser
- patchy can-i - Show which actions your RBAC allows
- patchy completion - Generate the autocompletion script for the specified shell
- patchy describe - Show the full detail of one resource
- patchy dev - Local test harnesses for generic-integration authors
- patchy expedite - Expedite a finding past the accumulation window and the queue
- patchy get - List patchy resources
- patchy mirror - Mirror upstream helm charts and OCI artifacts into a platform registry
- patchy resume - Resume a suspended finding
- patchy retry - Retry a failed finding from the state it failed in
- patchy review - Read an agent's report on a finding
- patchy suspend - Suspend a finding, pausing its progress through the pipeline