dataiku-sdk 4.1.0 → 4.2.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.
Files changed (46) hide show
  1. package/dist/build-metadata.json +1 -1
  2. package/dist/packages/types/src/index.d.ts +2 -0
  3. package/dist/packages/types/src/index.js +2 -0
  4. package/dist/src/cli/command-syntax.json +2426 -1262
  5. package/dist/src/cli/commands/future.js +7 -2
  6. package/dist/src/cli/commands/index.js +4 -0
  7. package/dist/src/cli/commands/messaging-channel.d.ts +17 -0
  8. package/dist/src/cli/commands/messaging-channel.js +385 -0
  9. package/dist/src/cli/commands/project-deployer.js +33 -0
  10. package/dist/src/cli/commands/project.js +30 -0
  11. package/dist/src/cli/commands/scenario.d.ts +6 -0
  12. package/dist/src/cli/commands/scenario.js +423 -13
  13. package/dist/src/cli/contract.js +17 -2
  14. package/dist/src/cli/flags.js +34 -0
  15. package/dist/src/cli/helpers/cleanup.js +11 -0
  16. package/dist/src/cli/list-shapes.js +5 -0
  17. package/dist/src/cli/plans.js +94 -2
  18. package/dist/src/cli/read-shapes.js +2 -1
  19. package/dist/src/cli/result-shapes.js +1 -0
  20. package/dist/src/cli/usage.js +7 -0
  21. package/dist/src/cli/version.d.ts +2 -2
  22. package/dist/src/cli/version.js +2 -2
  23. package/dist/src/client.d.ts +11 -0
  24. package/dist/src/client.js +21 -2
  25. package/dist/src/generated/action-output-schemas.json +82 -0
  26. package/dist/src/index.d.ts +1 -0
  27. package/dist/src/index.js +1 -0
  28. package/dist/src/resources/bundles.d.ts +18 -0
  29. package/dist/src/resources/bundles.js +26 -0
  30. package/dist/src/resources/futures.d.ts +3 -0
  31. package/dist/src/resources/futures.js +5 -1
  32. package/dist/src/resources/messaging-channels.d.ts +83 -0
  33. package/dist/src/resources/messaging-channels.js +108 -0
  34. package/dist/src/resources/projects.d.ts +24 -0
  35. package/dist/src/resources/projects.js +36 -0
  36. package/dist/src/resources/scenario-authoring.d.ts +52 -0
  37. package/dist/src/resources/scenario-authoring.js +216 -0
  38. package/dist/src/resources/scenarios.d.ts +128 -11
  39. package/dist/src/resources/scenarios.js +273 -43
  40. package/dist/src/utils/messaging-channel-secrets.d.ts +17 -0
  41. package/dist/src/utils/messaging-channel-secrets.js +114 -0
  42. package/package.json +1 -1
  43. package/plugin.json +1 -1
  44. package/skills/dataiku-dss/SKILL.md +4 -3
  45. package/skills/dataiku-dss/references/notifications.md +29 -0
  46. package/skills/dataiku-dss/references/troubleshooting.md +1 -1
package/skills/dataiku-dss/references/troubleshooting.md CHANGED
@@ -4,7 +4,7 @@
4
4
 
5
5
  - Code/SQL: use `--file`/`--sql-file`; shells, especially PowerShell, mangle quotes, `$`, and multiline text. Non-UTF-8 consoles (e.g. Windows cp1252): write non-ASCII results to UTF-8 files or `--output PATH`, not the console.
6
6
  - Build errors: `dss job log <id> --errors-only` selects errors/tracebacks. Plain `job log` prints the last 100 lines (`log_truncated`); for full logs, use `--output PATH` without `--errors-only`. Logs may arrive as one JVM-noisy line; `Error in Python process: At line <N>` identifies the payload source line.
7
- - Failed scenario: `dss scenario get-run ID RUNID` gives `failure` {stepId, jobId, dataset, message} and `next` argv (`job log JOBID --errors-only`); `run-and-wait` failures carry both.
7
+ - Failed scenario: `dss scenario get-run ID RUNID` gives `failure` {stepId, jobId, dataset, message} and `next` argv (`job log JOBID --errors-only`); `run-and-wait` failures carry both. `scenario run` without `--wait` returns a trigger run id: `scenario get-run-for-trigger` resolves it (`CANCELLED`: already running). Last finished run: `last-runs --only-finished --limit 1`.
8
8
  - Schemas: code recipes set output schemas at run time. Visual/SQL query recipes: `recipe create` fills created or empty outputs (`outputSchemaUpdated`); `recipe set-payload` updates empty or DSS-derived ones, warns `recipe_output_schema_outdated` for hand-edited ones. Apply with `dss recipe update-schema NAME` (one recipe), `dss flow propagate-schema DATASET --wait` (every downstream recipe), or build `--auto-update-schema`. `built_dataset_has_no_columns`: the DONE build wrote nothing. `nothing_to_build` (exit 4): no recipe writes the managed target. Manual columns: `dss dataset refresh-schema NAME --data-file columns.json`. `dss dataset validate-build` catches file-backed misconfiguration.
9
9
  - `Inline` (editable) datasets: the public API cannot write rows, so `dataset create` rejects them; use `UploadedFiles` + `dataset upload-file`, or a python recipe output. `code run` is a scenario step; some DSS versions refuse dataset writes there.
10
10
  - `dss dataset download`: default 100k rows; result `{ path, rows, truncated, limit }`. If truncated, raise `--limit`. Specify `--output` or read the `dataset_download_default_location` path warning. CSV is spreadsheet-safe; `--raw-data` retains formula prefixes. For large tables, aggregate in SQL or use a recipe.