@lightdash/cli 1.110.0 → 1.111.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.
|
@@ -16,7 +16,7 @@ You are editing a Lightdash **data app** that was created or downloaded with the
|
|
|
16
16
|
|
|
17
17
|
- The one sanctioned path to a third-party API is `lightdash.externalFetch('<alias>', ...)` against an **external connection** a project admin configured and linked to this app (see the `lightdash-data-app` skill).
|
|
18
18
|
- The app's links are declared in this folder's `lightdash-app.yml` under `externalConnections` (`- alias: stripe` / `connectionSlug: stripe-api`). When the key is present, upload reconciles the app's links to match it exactly — so to link a connection that **already exists in the project**, add its `{alias, connectionSlug}` entry and upload. Do not remove entries casually: an entry removed from the list (or an empty list) unlinks on upload, and a manifest without the key leaves links unchanged.
|
|
19
|
-
- Watch the upload output: a `connectionSlug` that doesn't exist in the target project is skipped with a warning (the app uploads, but `externalFetch` on that alias fails at runtime)
|
|
19
|
+
- Watch the upload output: a `connectionSlug` that doesn't exist in the target project is skipped with a warning (the app uploads, but `externalFetch` on that alias fails at runtime). Linking requires either the admin-level `manage:ExternalConnection` permission or an admin-enabled connection plus permission to manage the target data app — if a link is skipped or forbidden, report it to the user instead of retrying.
|
|
20
20
|
- If the app needs an API with **no existing connection**, **stop and say so** — do not vendor an HTTP client or try to reach it another way. An admin must create the connection first (in project settings, or as code: `lightdash download --include-external-connections`, edit `lightdash/external-connections/<slug>.yml`, `lightdash upload` with the secret in `LIGHTDASH_EXTERNAL_CONNECTION_SECRET_<SLUG>`); then it can be linked via the manifest as above.
|
|
21
21
|
|
|
22
22
|
## Library boundaries — build with what's preinstalled
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lightdash/cli",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.111.0",
|
|
4
4
|
"description": "Lightdash CLI tool",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -41,8 +41,8 @@
|
|
|
41
41
|
"unique-names-generator": "4.7.1",
|
|
42
42
|
"uuid": "11.1.1",
|
|
43
43
|
"yaml": "2.8.3",
|
|
44
|
-
"@lightdash/common": "1.
|
|
45
|
-
"@lightdash/warehouses": "1.
|
|
44
|
+
"@lightdash/common": "1.111.0",
|
|
45
|
+
"@lightdash/warehouses": "1.111.0"
|
|
46
46
|
},
|
|
47
47
|
"devDependencies": {
|
|
48
48
|
"@types/inquirer": "8.2.4",
|