RFC 0052: managed cluster CLI and device login - #629
Merged
Conversation
aaltshuler
marked this pull request as ready for review
September 5, 2026 12:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Add managed cluster operations to the existing
omnigraphCLI. A folder's.omnigraph/contextroutes plan/apply/status/history/cancel through the Intent API, and device login stores a short-lived control-plane session in the OS keychain. Applying an exact saved plan depends on current permissions, with no separate managed approval workflow.Backing issue / RFC
RFC 0052 is accepted and implemented after maintainer-authorized review. Its contract covers control-plane operations only; data access remains a separate increment.
Behavior and boundaries
cluster --directretains the existingcluster.yamlroot behavior.--plan. Plan/apply retries retain the idempotency key and request body; cancellation/abandonment retry by run id. Local wait timeout leaves accepted work running.Validation
just e2e-cli, using the actual native CLI binary, passed the full kind loop: exact-plan apply, receipt/readiness, idempotency, abandonment replay, cancellation, timeout, and no direct-storage fallback.Checklist
docs/dev/invariants.md; no invariant weakened or deny-list item introduced.Companion: og-control-plane #25, stacked on #24. The native kind proof takes an explicit companion CLI binary; an automatic cross-repository CI pin remains outside this PR.