FROSADO / onecloudriver / 33999112520

81%

main: 81%

Build Type

Pull #148

github

Committed by FROSADO

Commit Message

feat(control): local Unix-socket HTTP/JSON control channel with /v1/info (Closes #147)

Add a local control channel so a second process (CLI, future UI) can talk
to the running mount without sharing its cache. The mount now listens on a
Unix socket inside the account cache directory and serves a versioned
HTTP/JSON API; this version publishes GET /v1/info (mount state, pid,
account, mountpoint, cache dir and effective config).

internal/control: HTTP server over a Unix socket (mode 0600, stale-socket
cleanup, graceful Close that unlinks the file) and a typed Go client whose
error handling maps dial failures to ErrNotRunning with errors.As instead
of string matching. The runtime daemon fields are owned by the server, so
a provider cannot spoof pid/startedAt/goVersion.

internal/fs: MountConfig.ControlSocket (default <cacheDir>/control.sock)
and start/stop of the server in fs.Mount, including the signal path that
exits via os.Exit.

cmd/onecloudriver: mount --control-socket flag ('off' disables; any path
overrides; otherwise derived from the final --cache-dir).

docs: SOCKET-API.md documents the published endpoint, schema, examples and
socket lifecycle; MANUAL (en/es) and man pages reference the channel and the
new flag.

Tests: unit tests for the server (info, 404/405, permissions, stale socket,
close, bind error) and client (success, not-running via ENOENT/ECONNREFUSED,
404/500, generic transport error) with no sleeps; fs provider coverage.
Coverage internal/control 82.2%, internal/fs provider 100%.

Pull Request Pull Request #148: feat(control): local Unix-socket HTTP/JSON control channel with /v1/info

Coverage Stats

173 of 238 new or added lines in 5 files covered. (72.69%)

2 existing lines in 1 file now uncovered.

6404 of 7878 relevant lines covered (81.29%)

2980.3 hits per line