homeboy 0.76.0

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

# `homeboy auth`

## Synopsis

```sh
homeboy auth <COMMAND>
```

## Description

Authenticate with a project’s API and store credentials in the OS keychain.

Authentication is scoped per project ID.

## Subcommands

### `login`

```sh
homeboy auth login --project <project_id> [--identifier <username_or_email>] [--password <password>]
```

If `--identifier` or `--password` are omitted, Homeboy prompts on stderr and reads from stdin.

### `logout`

```sh
homeboy auth logout --project <project_id>
```

### `status`

```sh
homeboy auth status --project <project_id>
```

## Output

JSON output is wrapped in the global envelope.

`data` is one of:

- `{ "command": "login", "project_id": "...", "success": true }`
- `{ "command": "logout", "project_id": "..." }`
- `{ "command": "status", "project_id": "...", "authenticated": true }`

Note: `command` is a tagged enum value (`login|logout|status`), and fields use snake_case (`project_id`).

## Related

- [api](api.md)
- [project](project.md)
- [JSON output contract](../architecture/output-system.md)