hirte-proxy(1)

📦 version 0.4.0, in epel 9

hirte-proxy 👑 — General Commands Manual

okay bestie, you're looking at the General Commands Manual page for hirte-proxy — that's hirte-proxy(1), no cap. It's lowkey a tiny command with big “proxy services on another agent” energy. Let's get into it 💖

NAME 🏷️

hirte-proxy — Proxy requesting services on other agents

SYNOPSIS 🎀

hirte-proxy [options] command

DESCRIPTION 🦋

Okay so Hirte is a service orchestrator tool intended for multi-node devices (e.g.: edge devices) clusters with a predefined number of nodes and with a focus on highly regulated environment such as those requiring functional safety (for example in cars). It's giving serious, regulated, “please don't vibe-check the safety systems” energy 🔥

A hirte-proxy uses the public API of hirte-agent provided on the local D-Bus to request services required by a local unit to be started or stopped on a remote node managed by another hirte-agent. Yep, it's the little proxy bestie making the remote-service ask happen ✨

The usage line is literally hirte-proxy [OPTIONS].

OPTIONS ✨

--help, -h — Print usage statement and exit. That's the whole option menu, bestie — short and iconic 💅

Commands 🛠️

hirte-proxy create [node_service] — Starts the hirte-proxy to call the CreateProxy method on the local hirte-agent to request a remote service to be started on the given node. hirte-proxy is exiting when starting the service has either succeeded or failed.
hirte-proxy remove [node_service] — Starts the hirte-proxy to call the RemoveProxy method on the local hirte-agent to request a remote service to be started on the given node. hirte-proxy is exiting when starting the service has either succeeded or failed.

Exit Codes 💀

On successfully starting the remote service, 0 is returned. Otherwise, 1 is returned. So slay = 0, not slay = 1 — that's the whole vibe check 😭