Cloud accounts

The forge keeps the provider tokens (a cloud vendor's API token) its repositories use, sealed. Four doors show them, all a forge admin's alone; anyone else finds no such page, screen, tool or route. No door ever returns a secret: a token is typed once, checked, sealed, and never drawn, kept in a note or sent back.

curl -H "authorization: Bearer $FORGE_TOKEN" "$FORGE_URL/api/v1/cloud/accounts"

Answers: 401 with no signed-in user, 403 for a read-only token (every vendor call is audited, so listing is a write-scoped act), 404 for anyone who is not a forge admin.

Not done: the route only lists. Attaching, rotating and removing stay on the page and in the terminal, where the token can be typed masked.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs