hivepaas login

Log in to an installation with an API key, made in its dashboard under Your Account, API Keys, with the actions the commands need: read, execute for deploy and restart, write for changes.

The secret is typed at the prompt, where it does not show, or read from stdin with --with-secret - never given as an argument, which the shell's history keeps and other users of the machine see in its list of processes. It goes to the OS keychain.

In CI nothing is stored: set HIVEPAAS_URL, and HIVEPAAS_API_KEY to <key id>:<secret> from the CI's secrets.

hivepaas login [URL] [flags]

Examples:

# At a terminal: the key id and the secret are asked for
hivepaas login https://paas.example.com

# From a file, or a password manager
hivepaas login https://paas.example.com --key-id 8b87cd98... --with-secret < hivepaas-key.txt
op read op://dev/hivepaas/secret | hivepaas login https://paas.example.com --key-id 8b87cd98... --with-secret

# A local installation, over http
hivepaas login localhost:10000

Flags:

Flag	Description
--insecure-storage	keep the secret in a file readable only by you when the OS keychain cannot be used
--key-id string	the API key's id
--name string	the context's name (default: the URL's host)
--with-secret	read the key's secret from stdin

The global flags apply to every command.