To configure a remote machine, a module used to reach for SSH and hand-write the commands it needed. That works until it doesn’t: every module reinvents the same plumbing slightly differently, and every one is a place for a subtle, hard-to-test mistake. Unified Management replaces that ad-hoc SSH with a small, fixed set of typed primitives that every module shares.
Why typed primitives
When “run this on the remote host,” “check whether this is healthy,” or “apply this configuration” are each a single well-defined operation instead of a bespoke shell string, the framework can test them once, handle their errors consistently, and give clear feedback when something goes wrong. Modules get to describe what they need done and leave the how — the connection, the retries, the transport — to primitives that are the same everywhere.
Where SSH belongs
The point isn’t to hide SSH; it’s to contain it. Remote access lives in one place — the shared transport and the primitive implementations — rather than being scattered across dozens of module hooks. That makes the whole surface auditable and lets a module author stop thinking about connection details entirely. Nearly every module hook has already moved off hand-built SSH; the remaining work is the firewall.