dflow login
Save an API origin and a bearer token after the API accepts the token.
dflow login
dflow login --email ADDRESS
dflow login --api URL --token TOKENFlags
--api optional origin. Omitted means the saved default from dflow context:use, or https://k8s.dflow.sh when none is saved. On a terminal, with no --email and no token flag, the CLI prints Email: and then Password:. --email skips the email question and prints Password:. The password is read with echo off. --token or --token-stdin saves an existing token and does not ask for a password. --token is visible in the process list. Without a terminal, an email, or a token, login exits 1. Globals.
What you see
The terminal prints aligned labels api and token. token is the word present. When the login is inside one workspace, org is that id. When it belongs to more than one, a table lists NAME, ID, and ROLE. The secret is not printed. URL rules above. Token is one string of 20 to 256 characters from A-Za-z0-9._~+/=-. The process list can see --token in M1; the CLI still must not write it to stdout, stderr, or logs. Exit 0: saved.
When it fails
Exit 1: bad URL, token, or symlink. Exit 2: API rejected the token. Exit 10: API unreachable. Exit 7 when the HTTP call exceeds 60s.
How is this guide?
Last updated on