dataiku-sdk 0.8.0 → 0.10.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 (41) hide show
  1. package/README.md +5 -4
  2. package/dist/src/cli.js +1668 -32
  3. package/dist/src/client.d.ts +61 -2
  4. package/dist/src/client.js +184 -5
  5. package/dist/src/index.d.ts +14 -1
  6. package/dist/src/index.js +13 -0
  7. package/dist/src/resources/api-deployer.d.ts +66 -0
  8. package/dist/src/resources/api-deployer.js +79 -0
  9. package/dist/src/resources/api-services.d.ts +38 -0
  10. package/dist/src/resources/api-services.js +50 -0
  11. package/dist/src/resources/applications.d.ts +56 -0
  12. package/dist/src/resources/applications.js +67 -0
  13. package/dist/src/resources/bundles.d.ts +53 -0
  14. package/dist/src/resources/bundles.js +103 -0
  15. package/dist/src/resources/continuous-activities.d.ts +27 -0
  16. package/dist/src/resources/continuous-activities.js +22 -0
  17. package/dist/src/resources/datasets.d.ts +6 -0
  18. package/dist/src/resources/datasets.js +15 -0
  19. package/dist/src/resources/discussions.d.ts +26 -0
  20. package/dist/src/resources/discussions.js +29 -0
  21. package/dist/src/resources/meanings.d.ts +41 -0
  22. package/dist/src/resources/meanings.js +33 -0
  23. package/dist/src/resources/metrics.d.ts +44 -0
  24. package/dist/src/resources/metrics.js +31 -0
  25. package/dist/src/resources/project-library.d.ts +38 -0
  26. package/dist/src/resources/project-library.js +82 -0
  27. package/dist/src/resources/projects.d.ts +70 -0
  28. package/dist/src/resources/projects.js +97 -0
  29. package/dist/src/resources/recipes.js +10 -8
  30. package/dist/src/resources/scenarios.d.ts +3 -0
  31. package/dist/src/resources/scenarios.js +8 -1
  32. package/dist/src/resources/statistics.d.ts +56 -0
  33. package/dist/src/resources/statistics.js +51 -0
  34. package/dist/src/resources/streaming-endpoints.d.ts +45 -0
  35. package/dist/src/resources/streaming-endpoints.js +36 -0
  36. package/dist/src/resources/webapps.d.ts +27 -0
  37. package/dist/src/resources/webapps.js +36 -0
  38. package/dist/src/resources/workspaces.d.ts +59 -0
  39. package/dist/src/resources/workspaces.js +31 -0
  40. package/dist/src/skill.js +6 -4
  41. package/package.json +1 -1
package/README.md CHANGED
@@ -8,21 +8,22 @@ Examples below assume the installed `dss` binary. From this checkout, use `./bin
8
8
  ## CLI contract
9
9
 
10
10
  - Success: stdout contains one JSON result.
11
- - Failure: stderr contains one JSON error envelope with `ok:false`, `error`, `code`, and `exitCode`.
12
- - `--verbose` may add HTTP trace lines to stderr.
11
+ - Failure: stderr contains one JSONL error event with `type:"error"`, `ok:false`, `error`, `code`, and `exitCode`.
12
+ - Non-fatal diagnostics and `--verbose` traces are JSONL stderr events (`type:"warning"` / `type:"trace"`); no prose trace lines are part of the contract.
13
13
  - `--fields a,b,c` projects those fields from an object or array-of-objects result; dotted paths (`a.b.c`) drill into nested objects, and missing fields become `null`; string and scalar results pass through unchanged.
14
14
  - No prompts, help screens, tables, banners, or prose output are part of the contract.
15
15
  - Exit codes: `0` success, `1` usage/configuration error, `2` DSS/internal error, `3` transient DSS error, `4` completed command with failed long-running DSS work.
16
16
  - The exit code is the success signal: chain mutations with `&&` and never infer success from piped output that discards the exit code (e.g. `dss ... 2>&1 | helper; echo done` reports success even when the command failed).
17
17
  - `--raw` is only for recipe payload commands. Without `--output`, stdout is raw bytes; with `--output PATH`, stdout is the JSON string equal to `PATH` and the file contains the exact raw bytes.
18
18
 
19
- Discover the complete machine-readable command surface:
19
+ Discover the agent protocol and complete machine-readable command surface:
20
20
 
21
21
  ```bash
22
+ dss agent contract
22
23
  dss commands run
23
24
  ```
24
25
 
25
- Agents should parse `commands run` before choosing syntax; inspect `flags`, `requiresAuth`, `requiresProject`, `sideEffect`, and `outputShape` instead of guessing.
26
+ Agents should parse `agent contract` once for protocol/schema compatibility, then parse `commands run` before choosing syntax; inspect `flags`, `structuredExamples`, `schemas`, `requiresAuth`, `requiresProject`, `sideEffect`, `unsafeOutputs`, and `outputShape` instead of guessing.
26
27
 
27
28
  ## Agent skill installation
28
29