The plan and apply workflow lets you preview changes before deploying them — similar to Terraform.
Plan
griffin plan compares your local monitor files against what’s deployed on the hub and shows the diff:
Use --monitor <name> to preview changes for only that monitor.
Example output:
CI/CD usage
griffin plan exits with code 2 when there are pending changes and 0 when everything is in sync. This makes it useful in CI pipelines:
Use --json for machine-readable output:
Apply
griffin apply pushes your local monitors to the hub:
Use --monitor <name> to create or update only that monitor. By default, it shows you what will change and asks for confirmation. Use flags to customize:
The prune flag
Without --prune, apply only creates and updates monitors. Monitors that exist on the hub but not locally are left untouched.
With --prune, monitors on the hub that don’t have a corresponding local monitor file are deleted.
Use --prune carefully. Always run griffin plan first to verify what will be deleted.
Validate and test (with optional filter)
You can restrict validation or local runs to a single monitor by name:
Typical workflow
