Skip to content
Fuse
Esc
↑↓navigate↵open⌘Jpreview
On this page

fuse connect

Add an orchestrator context and make it active

fuse connect <url> [flags]

Stores an orchestrator’s base URL and bearer token as a named context and makes it active. <url> is the orchestrator root (scheme://host:port), without a /v1 suffix.

Flags

Flag Purpose
--token Bearer token for the orchestrator.
--name Context name. Defaults to the URL’s hostname if omitted.
--master Mark this token as the master token, required for fuse apikeys. See below.
--no-verify Skip the pre-save probe (for offline or scripted setup).

Examples

fuse connect http://localhost:8080
fuse connect https://orchestrator.example.com --token "$FUSE_TOKEN" --name prod --master

Notes

Before saving, connect probes the URL to confirm it is really a fuse orchestrator (via the unauthenticated GET /v1/version) and, if you passed a --token, that the orchestrator accepts it. Each failure names the layer that failed rather than surfacing an opaque error one command later:

  • nothing listening: no orchestrator at <url> (connection refused). is it running? the orchestrator default port is 8080. pass --no-verify to skip this check
  • wrong service or port: <url> is not a fuse orchestrator (got Server: fc-agent/0.1). the orchestrator default port is 8080; 8090 is the host agent
  • wrong token: orchestrator at <url> rejected the token. this must be ORCH_AUTH_TOKEN, not the host-agent token

Pass --no-verify to skip the probe for offline or scripted setup.

--master is informational on the client side, it only records how the context was created so fuse apikeys can warn you early. The server is what actually enforces whether the token carries master privileges, so marking a non-master token does not grant it anything.

With no --token, connecting only works against an orchestrator running in insecure/dev mode (no ORCH_AUTH_TOKEN set), the CLI prints a warning when you do this rather than failing outright, since it’s a legitimate local-dev workflow. See Authentication for the full token model.

Running fuse connect again with the same derived or explicit --name overwrites that context’s URL and token in place rather than erroring, useful for rotating a token without a separate remove-then-reconnect step.

Was this page helpful?