@lightdash/cli 1.154.0 → 1.154.2
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 +2 -0
- package/dist/.tsbuildinfo +1 -1
- package/dist/handlers/login.d.ts +8 -0
- package/dist/handlers/login.d.ts.map +1 -1
- package/dist/handlers/login.js +21 -2
- package/dist/handlers/login.test.d.ts +2 -0
- package/dist/handlers/login.test.d.ts.map +1 -0
- package/dist/handlers/login.test.js +24 -0
- package/dist/index.js +3 -1
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -159,6 +159,8 @@ The `--non-interactive` flag is designed for environments where interactive prom
|
|
|
159
159
|
| `CI=true` | Equivalent to `--non-interactive` |
|
|
160
160
|
| `LIGHTDASH_API_KEY` | API token for authentication (can be used instead of `--token`) |
|
|
161
161
|
|
|
162
|
+
Credentials resolve in the usual order: command flags, then environment variables, then the config file written by `lightdash login`. So a `LIGHTDASH_API_KEY` left in your shell profile is used ahead of your saved login — `lightdash login` warns when this is the case, and `unset LIGHTDASH_API_KEY` restores the saved token.
|
|
163
|
+
|
|
162
164
|
### Example Automation Scripts
|
|
163
165
|
|
|
164
166
|
```bash
|