omnigraph/crates/omnigraph-cli/tests
aaltshuler f3374ac6dc feat(cli): resolve cluster actor via the per-operator config cascade
Cluster FACTS stay unlayered (cluster.yaml only), but the operator's
identity is a per-operator fact — exactly the per-operator omnigraph.yaml's
permanent job, and the cascade every data-plane write already uses. cluster
apply/approve now resolve: --as flag wins and skips any config read
entirely (containers and CI stay config-free); without it, the standard cwd
search supplies cli.actor, with a malformed config failing loudly and
actionably ('pass --as to skip this lookup') rather than silently dropping
attribution. approve's no-actor error now names both sources.

Tests pin the contract from both sides: cli.actor is the no-flag default
for apply (echoed actor) and approve (approved_by), the flag overrides it,
a malformed omnigraph.yaml in cwd breaks nothing except the no-flag actor
lookup, and a conflicting well-formed one leaks nothing into cluster
outputs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-10 22:29:49 +03:00
..
support test(cli): comprehensive full-cycle cluster e2e with a live server 2026-06-10 18:07:29 +03:00
cli.rs feat(cli): resolve cluster actor via the per-operator config cascade 2026-06-10 22:29:49 +03:00
system_local.rs test(cli): address review — assert schema-show success, document exit-code stance, add e2e opt-out 2026-06-10 19:05:12 +03:00
system_remote.rs Stored-query registry foundation + config/CLI RFC-002 (#128) 2026-06-01 22:50:31 +02:00