homeboy 0.31.1

CLI for multi-component deployment and development workflow automation
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69

# `homeboy ssh`

## Synopsis

```sh
# Non-interactive discovery (JSON output):
homeboy ssh list

# Connect (interactive when COMMAND is omitted):
homeboy ssh [OPTIONS] [ID] [COMMAND]
```

## Subcommands

### `list`

Lists configured SSH server targets. This is safe for CI/headless usage.

```sh
homeboy ssh list
```

## Arguments and flags

- `[ID]`: project ID or server ID (project wins when both exist). Optional when using `--project` or `--server`.
- `--project <PROJECT>`: force project resolution
- `--server <SERVER>`: force server resolution
- `[COMMAND]` (optional): command to execute (omit for interactive shell). Note: currently parsed as a single argument; multiple words may require shell quoting.


## JSON output

### `ssh list`

> Note: output is wrapped in the global JSON envelope described in the [JSON output contract](../architecture/output-system.md). The object below is `data`.

```json
{
  "action": "list",
  "servers": [
    {
      "id": "...",
      "name": "...",
      "host": "...",
      "user": "...",
      "port": 22,
      "identity_file": null
    }
  ]
}
```

Note: `action` is produced by the tagged enum output (`SshOutput`).

### Connect (`homeboy ssh [OPTIONS] [ID] [COMMAND]`)

The connect action uses an interactive SSH session and does not print the JSON envelope (it is treated as passthrough output).

When `command` is provided, it is passed to the remote shell via the interactive session.

Note: the CLI still computes a JSON `data` object internally for this action, but it is not printed in interactive passthrough mode.

## Exit code

Exit code matches the underlying SSH session/command exit code.

## Related

- [server](server.md)