Signing In
For everyday use
atlas login --url https://atlas.cloudbeat.io -u you@company.comYou'll be prompted for your password. The session lasts 8 hours.
Credentials are stored in ~/.atlas/config.json, readable only by you.
atlas whoami # who am I, and in which account
atlas logout # forget the credentialFor CI: API tokens
A password prompt is no use in a pipeline, and storing a human's password is worse. Create an API token instead.
On your Atlas instance, go to Profile → API tokens and create one. The token is shown once — copy it then.
atlas login --token atlas_pat_...Or, better in CI, pass it as an environment variable and don't store it at all:
export ATLAS_TOKEN=atlas_pat_...What a token can and can't do
A token acts as the person who created it, with the same permissions and in one fixed account. If that person's access is reduced or removed, the token follows immediately.
Two things it deliberately cannot do:
- create more tokens
- change a password
So a leaked pipeline token can't mint replacements for itself or lock you out. Revoking it on the Profile page stops it working at once.
Scope the token to one account
If you belong to several accounts, switch to the one the pipeline should use before creating the token. The token is fixed to whichever account was active when it was made.
Treat it like a password
A token is a credential. Put it in your CI system's secret store, not in the repository, and not in a build log.
Settings and precedence
Command-line options win over environment variables, which win over the saved configuration file.
| Variable | Meaning |
|---|---|
ATLAS_URL | your Atlas instance |
ATLAS_TOKEN | API token |
ATLAS_PROJECT | project to use when --project is omitted |
ATLAS_DEBUG | set to any value to print full error details |
To avoid repeating yourself:
atlas config set url https://atlas.cloudbeat.io
atlas config set project SHOP