@tsuga/cli 1.19.0 → 1.21.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -0
- package/dist/cli.js +63 -61
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -70,6 +70,10 @@ tsuga auth logout
|
|
|
70
70
|
|
|
71
71
|
After `tsuga auth login`, commands work without an Operation API key.
|
|
72
72
|
|
|
73
|
+
On macOS the session is stored in your Keychain under the service `tsuga-cli` (one item per API URL), so it never lands on disk in plaintext. If the Keychain is unavailable or rejects the write, the CLI says so and falls back to the config file. Everywhere else the session is written to the config file. `tsuga auth logout` removes it from both.
|
|
74
|
+
|
|
75
|
+
Sessions renew themselves: the login also saves a refresh token, and the CLI exchanges it for a new access token when the current one is within five minutes of expiry. You log in again when the refresh token expires, when it is revoked, or when the session predates refresh support.
|
|
76
|
+
|
|
73
77
|
### Operation API key
|
|
74
78
|
|
|
75
79
|
For non-interactive use (CI, scripts), authenticate with an Operation API key. Generate one from your [Tsuga account settings](https://app.tsuga.com/settings/api-keys?operation=true), then save it once:
|