Documentation
¶
Overview ¶
Command cloop-forward is the device forwarder as a standalone binary: it dials a cloop hub and bridges exactly one configured USB device or network interface, and does nothing else (Task 20429).
It is deliberately tiny. The full `cloop forward` subcommand does the same thing, but it lives in a binary that also contains an orchestrator, a web dashboard and a hundred other commands. The trust model here is "the agent runs in an isolated environment in the cloud with limited access to on-prem hardware", and the aperture through which that access is granted should be as small as the job: this main imports pkg/deviceforward and nothing of the rest of cloop, so what runs on the machine wired to the hardware is a byte pump with a credential, not a product.
Enrollment, revocation and listing are hub-side operations — run them with the full `cloop forward enroll|revoke|list` on the control plane. This binary only runs a forwarder that someone already enrolled.
Source Files