hull policy list
Synopsis
hull policy list prints the policy rules a package declares under
<package-path>/policies/, one per line, with each rule’s severity. It does
not evaluate anything or read a manifest.
When to use it
- To audit what guardrails a package self-imposes before you consume it — especially an upstream package you did not write.
- To confirm which rules
hull policy checkwill run.
What happens
- Loads every rule from
<package-path>/policies/*.yaml. - Prints each rule as
name [severity], in declaration order. - Reads only local files — no manifest, no cluster, no network.
Usage
hull policy list <package-path> [flags]
Flags
Inherits the global flags.
Worked example
INPUT — two rules under mychart/policies/:
# mychart/policies/images.yaml
name: no-latest-tag
severity: deny
match: { kinds: [Deployment] }
require: { imageNotTagged: true }
---
# mychart/policies/scale.yaml
name: min-replicas-3
severity: warn
match: { kinds: [Deployment] }
require: { minReplicas: 3 }
Run it:
hull policy list ./mychart
OUTPUT — each rule and its severity:
no-latest-tag [deny]
min-replicas-3 [warn]
deny rules fail hull policy check; warn rules only print.
See also
policy— the parent commandpolicy check— actually evaluate the rulesinstall— apply the package once it passes