ctl-architecture

What problem does it solve?

Edgion configuration sync issues are hard to diagnose because the same resource can exist in one tier (center, controller server cache, or gateway client cache) but not in another. This Skill helps you pinpoint where the mismatch happens by documenting how edgion-cli targets each tier and routes its API calls.

Core Features & Use Cases

• Three target modes (center/server/client): Connects to the Controller Admin API or to gateway-side cache endpoints with clear default ports and read/write capability differences.
• Cache-tier inspection for sync troubleshooting: Compares resource presence and behavior across ConfCenter → ServerCache → ClientCache to locate breakdown stages.
• Deterministic HTTP client behavior: Uses a structured EdgionClient abstraction (HTTP requests over reqwest) and well-defined API routes per target.
• Operational commands support: Guides use of get/apply/delete/reload plus non-targeted certificate generation for conf_sync mTLS.
• Structured output options: Produces table/json/yaml/wide outputs so you can diff results across tiers.

Quick Start

Run the skill by executing edgion-cli get httproute my-route -n default -o yaml first in center mode, then in server mode, then in client mode to see exactly where the sync diverges.