monedula-acl-rbac report

Re-print plan.json's report in alternate formats. Usage and flags for monedula-acl-rbac report.

Reference 20 of 29

Reference for monedula-acl-rbac-converter v0.10.0

Updated 2 October 2026

usage

monedula-acl-rbac report [flags]

Render the report embedded in plan.json (text, markdown, or json).

By default exits 0 on successful render, regardless of whether the plan contains UNMAPPED or REJECTED bindings - viewing a plan should not fail. Pass --strict to make the command exit with a plan-error code when the plan is unhealthy (useful in CI scripts that gate the next step on a clean report).

Read-only: this command does not change the cluster.

Flags

Flag	Type	Default	Description
`--plan`	string		Path to plan.json
`--format`	string	`text`	text\|markdown\|json
`--out`	string		Output path (default: stdout)
`--strict`	bool		Exit non-zero when the plan has UNMAPPED or REJECTED items (default: render and exit 0)

Global flags

Flag	Type	Default	Description
`--log-format`	string	`text`	Log output format (text\|json); set MONEDULA_ACL_RBAC_LOG_FORMAT to override the default.
`--log-level`	string	`info`	Log level (debug\|info\|warn\|error); set MONEDULA_ACL_RBAC_LOG_LEVEL to override the default.

Examples

examples

monedula-acl-rbac report --plan runs/2026-05-21T10-00-00Z/plan.json --format markdown

Exit codes

Code	Meaning
`0`	Success.
`1`	Usage error: missing required flag, malformed argument, or unknown subcommand.
`2`	Input error: unparseable ACLs or missing/malformed config (rules, principals, scopes, or vars files).
`3`	Only with --strict: the plan has unresolved unmapped or rejected items. Without --strict, report exits 0.
`4`	Any other error: failures the CLI does not classify (for example an unrecognized --format value) fall back to exit code 4.