snoutdata 0.20.0 → 0.21.0

package/README.md

@@ -60,8 +60,9 @@ export SNOUTDATA_ACCESS_TOKEN=sdt_...   # made once by a person: snoutdata token
 `--expires`. Made with `--project REF`, it reaches that one project and nothing else. It is what
 CI and an agent
 should use: a script's behaviour should not depend on who happens to be logged in on the machine
-it runs on. Failing that, `~/.snoutdata/auth.json` (written by `snoutdata login`, mode 0600),
-whose session renews itself as it is used.
+it runs on. Failing that, the profile's session: `~/.snoutdata/auth.json` (written by
+`snoutdata login`, mode 0600), or `~/.snoutdata/auth.NAME.json` for a named profile, whose session
+renews itself as it is used.
 
 The token is exchanged for a short-lived session by the control plane, so row-level security is
 still the only thing deciding what it can see.
@@ -100,8 +101,9 @@ snoutdata login --sso                 # your company's identity provider; asks f
 snoutdata login --sso --domain acme.com   # or name the domain and skip the question
 snoutdata login --device              # print a code to type into a browser anywhere
 snoutdata login --no-browser          # print the URL instead of opening one
-snoutdata logout
-snoutdata whoami
+snoutdata login --profile acme        # a second account, kept beside the first
+snoutdata logout [--all]              # this profile, or every one
+snoutdata whoami [--all]              # --all: every profile signed in here
 snoutdata tokens create --name ci [--expires DAYS] [--project REF]
 snoutdata tokens list
 snoutdata tokens revoke <id|sdt_prefix>
@@ -189,7 +191,12 @@ Every command takes `--json`, `--quiet` and `--help`, and anything that waits ta
 **A project**, in order: `--ref`, then `SNOUTDATA_PROJECT`, then `.snoutdata/project.json` in
 this folder or a parent.
 
-**A token**, in order: `SNOUTDATA_ACCESS_TOKEN`, then `~/.snoutdata/auth.json`.
+**A token**, in order: `SNOUTDATA_ACCESS_TOKEN`, then the profile's session
+(`~/.snoutdata/auth.json`, or `auth.NAME.json` for a profile).
+
+**A profile**, in order: `--profile`, then `SNOUTDATA_PROFILE`, then the profile recorded in
+`.snoutdata/project.json` (`link --profile NAME` writes it), then the default. Any command takes
+`--profile`, so one machine stays signed in to several accounts.
 
 **Sign-in, when there is no credential and a person is present**, in order: SnoutData
 Studio if it is running here and willing, then a browser, then a pairing code for a