datumctl v0.17.0 — Multi-environment logins that stay separate

[scotwells]

Signing in to two Datum Cloud environments with the same email address used to quietly break your login. v0.17.0 fixes that at the root, heals existing installs automatically, and makes datumctl auth switch show exactly which account you're on.

---

Fixed: two environments no longer clobber each other's login (#237)

Logging in to production and staging with the same email address stored both sessions under a single credential slot, so the second sign-in silently overwrote the first. datumctl auth list still showed both accounts, but after datumctl auth switch the CLI would send one environment's token to the other's API and fail — usually with a confusing:

error: You must be logged in to the server (the server has asked for the client to provide credentials)

To anyone hitting it, it looked like switching accounts randomly corrupted the login.

Each login is now stored separately per environment, so switching accounts, automatic token refresh, and datumctl logout all stay scoped to the right one. Existing installs upgrade themselves the next time they authenticate — there's nothing to run, and the migration never removes a token it can't first preserve.

Note

If one of your logins was already overwritten before upgrading, that single token can't be recovered. Run datumctl login --hostname <that environment's auth host> once to re-establish it; every other environment keeps working with no action.

datumctl auth switch now shows your active account (#237)

The account you're currently signed in as is labeled (active) in the session picker, and the picker opens on it — so it's always clear what you're switching from:

Which login session?
> swells@datum.net  (api.staging.env.datum.net)  (active)
  swells@datum.net  (api.datum.net)

---

Full changelog: datum-cloud/datumctl@v0.16.0...v0.17.0