mammoth-cli 2.0.51__tar.gz → 2.0.53__tar.gz

{mammoth_cli-2.0.51 → mammoth_cli-2.0.53}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.51
+Version: 2.0.53
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk
@@ -17,7 +17,7 @@ Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Python: <3.15,>=3.12
 Requires-Dist: jsonschema>=4.20
 Requires-Dist: keyring<26,>=25.7
-Requires-Dist: mammoth-io<0.8,>=0.7.23
+Requires-Dist: mammoth-io<0.8,>=0.7.24
 Requires-Dist: platformdirs<5,>=4.10
 Requires-Dist: pydantic<3,>=2.13
 Requires-Dist: pyyaml<7,>=6

{mammoth_cli-2.0.51 → mammoth_cli-2.0.53}/mammoth_cli/__init__.py

@@ -6,7 +6,7 @@ not implement a second HTTP client and does not call private SDK members.
 
 from __future__ import annotations
 
-__version__ = "2.0.51"
+__version__ = "2.0.53"
 
 # The versioned machine output envelope contract.
 SCHEMA_VERSION = 1

{mammoth_cli-2.0.51 → mammoth_cli-2.0.53}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mammoth-cli
-version: 2.0.51
+version: 2.0.53
 description: "Use Mammoth Analytics from a terminal: install or authenticate the CLI, discover its live command contract, and safely manage projects, data, views, pipelines (join, merge, pivot, filter, clean), dashboards, exports, and handoffs."
 ---
 

{mammoth_cli-2.0.51 → mammoth_cli-2.0.53}/mammoth_cli/bundled_skill/mammoth-cli/references/jobs-drafts.md

@@ -9,7 +9,9 @@ happens with the job, so you do not have to guess:
   envelope says `"status": "done"` and `"pipeline_state": "ready"`: the
   pipeline has finished, so do not poll its `future_id`; verify the values
   with `view data get`. (With SDK ≤ 0.7.13 the same envelope said
-  `"processing"`; it meant the same thing.)
+  `"processing"`; it meant the same thing.) If the view's auto-run is off,
+  the same call instead returns `"status": "staged"` with a `message`
+  naming `view draft submit VIEW_ID` — run that to actually execute it.
 - Only a `returns_job` command normally needs you to wait on the job id
   explicitly:
   ```bash
@@ -27,7 +29,13 @@ is `outcome_unknown`. Re-read the exact target and scope before replaying it;
 the operation may already have committed.
 
 ## Draft mode
-Batch several pipeline edits, then submit them together:
+With auto-run on (the normal mode), every pipeline change reruns the whole
+pipeline. On a big view, say 1M rows, adding 3 rules runs it 3 times. When you
+know up front that you will make several changes, enter draft mode, add them
+all, then submit: the pipeline runs once. A staged change has no data until the
+submit, so read back after it, not before. A view already in draft mode (auto-run
+off) answers each change with `"status": "staged"`; add the rest, then submit
+once.
 ```bash
 mammoth view draft enter 1039 --project 180
 mammoth view transform add-column 1039 --project 180 \

{mammoth_cli-2.0.51 → mammoth_cli-2.0.53}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/transforms.md

@@ -52,6 +52,21 @@ only signal is the task's own `transform_status` (`view task get`/`view task
 list` always read it at full detail). `DONE` means the step actually
 produced output; `ERROR` or `REFERROR` means it did not, even though the
 mutation "succeeded".
+- `split` makes new columns and `unnest` turns columns into label/value
+  rows; neither gives one row per delimited value. For one row per value,
+  use `add-sql` over `"view:VIEW_ID"`, selecting the other columns plus
+  `TRIM(UNNEST(string_split(COALESCE(tags, ''), ','))) AS tag`. Keep every
+  row -- a blank or NULL value stays as one row with an empty tag, and
+  `COALESCE` is what keeps the NULL rows, since DuckDB's `UNNEST` of NULL
+  yields zero rows (verified: drop the `COALESCE` and a NULL row vanishes).
+  Never add a `WHERE` that drops rows the user did not ask to drop. Verify
+  by row count: the result should equal the sum of each row's value count,
+  with a blank or NULL counting as 1.
+
+```bash
+mammoth view transform add-sql VIEW_ID --project PROJECT_ID \
+  --input '{"dataset_id":DATASET_ID,"query":"SELECT event_id, user_id, event_time, payload, TRIM(UNNEST(string_split(COALESCE(tags, '\'''\''), '\'','\''))) AS tag FROM \"view:VIEW_ID\""}'
+```
 
 These examples use the released route IDs and input shapes documented by the
 command manifest; substitute only observed view IDs and display names:

{mammoth_cli-2.0.51 → mammoth_cli-2.0.53}/mammoth_cli/commands/folder.py

@@ -156,8 +156,9 @@ def folder_find(invocation: Invocation) -> HandlerResult:
     return {
         "matches": matches,
         "projects_searched": len(projects),
-        "projects_truncated": invocation.project is None
-        and len(projects) >= _MAX_PROJECTS_SEARCHED,
+        "projects_truncated": (
+            invocation.project is None and len(projects) >= _MAX_PROJECTS_SEARCHED
+        ),
     }, meta
 
 
@@ -240,13 +241,39 @@ def folder_update(invocation: Invocation) -> HandlerResult:
 
 
 def folder_move(invocation: Invocation) -> HandlerResult:
-    """Move resources into a target folder in the active project."""
+    """Move resources into a target folder in the active project.
+
+    One of ``resource_ids``, ``dataset_ids``, or ``view_ids`` is required.
+    ``dataset_ids``/``view_ids`` take the plain ids ``dataset get``/``view
+    get`` return and are resolved to resource ids by the SDK; ``resource_ids``
+    is for when the caller already has a resource id from elsewhere.
+    """
     project_id = require_project(invocation)
-    document = invocation.load_input()
-    resource_ids = _require_field(document, "resource_ids")
-    kwargs: dict[str, Any] = {"resource_ids": resource_ids, "project_id": project_id}
-    assert document is not None
-    _forward_optional(document, kwargs, ("target_folder_resource_id", "source_folder_resource_id"))
+    document = invocation.load_input() or {}
+    kwargs: dict[str, Any] = {"project_id": project_id}
+    _forward_optional(
+        document,
+        kwargs,
+        (
+            "resource_ids",
+            "dataset_ids",
+            "view_ids",
+            "target_folder_resource_id",
+            "source_folder_resource_id",
+        ),
+    )
+    if not any(field in kwargs for field in ("resource_ids", "dataset_ids", "view_ids")):
+        raise CliError(
+            code=CODE_MISSING_FIELD,
+            message=(
+                "This command requires one of 'resource_ids', 'dataset_ids', " "or 'view_ids'."
+            ),
+            exit_status=EXIT_USAGE,
+            hint=(
+                "Pass it via --input, e.g. "
+                '--input \'{"dataset_ids": [1407], "target_folder_resource_id": 3445}\'.'
+            ),
+        )
     with open_service(invocation) as (service, auth):
         data = service.call(_symbol(invocation), **kwargs)
     return data, _meta(invocation, auth.workspace_id, project_id)

{mammoth_cli-2.0.51 → mammoth_cli-2.0.53}/pyproject.toml

@@ -1,13 +1,13 @@
 [project]
 name = "mammoth-cli"
-version = "2.0.51"
+version = "2.0.53"
 description = "Command-line interface for the Mammoth Analytics platform"
 authors = [{name = "Mammoth Analytics", email = "support@mammoth.io"}]
 readme = "README.md"
 license = "LicenseRef-Proprietary"
 requires-python = ">=3.12,<3.15"
 dependencies = [
-    "mammoth-io (>=0.7.23,<0.8)",
+    "mammoth-io (>=0.7.24,<0.8)",
     "typer (>=0.27,<0.28)",
     "rich (>=15,<16)",
     "platformdirs (>=4.10,<5)",

{mammoth_cli-2.0.51 → mammoth_cli-2.0.53}/spec/manifests/commands/folder.yaml

@@ -260,8 +260,11 @@ commands:
   - CT-FOLDER-MOVE-ERROR
   draft_test: null
   undo_test: null
-  known_restrictions: 'B05 FOLDER_MOVE_NO_WAIT: SDK returns ObjectJobSchema but exposes no public wait
-    method; do not advertise --wait/--no-wait.'
+  known_restrictions: Prefer dataset_ids/view_ids (the plain ids dataset get/view get return) over resource_ids
+    -- the SDK resolves them to resource ids for you. resource_ids itself takes each item's resource id,
+    not a dataset/view's own id. target_folder_resource_id is the destination folder's id field, exactly
+    as folder list/folder get/folder create return it (NOT the folder's resource_id field, despite this
+    parameter's name).
   reviewed_by: primary
 - command_id: folder.root
   command_path: folder root

{mammoth_cli-2.0.51 → mammoth_cli-2.0.53}/spec/manifests/commands/view.yaml

@@ -2474,8 +2474,9 @@ commands:
   - CT-VIEW-EXPORT-POWERBI-ERROR
   draft_test: null
   undo_test: null
-  known_restrictions: The handler enum and helper exist, but the pure contract omits it; confirm camel-case
-    clientId against the pinned server before enabling. See IO-EXPORT-HANDLERS blocker.
+  known_restrictions: Needs the Power BI account username and password, the Azure AD app's client_id, and
+    the target Power BI dataset and table; the password is a secret field, so pass it in the request file,
+    never in argv.
   reviewed_by: primary
 - command_id: view.export.publish-db
   command_path: view export publish-db

{mammoth_cli-2.0.51 → mammoth_cli-2.0.53}/spec/manifests/sdk-catalog.source.yaml

@@ -2507,8 +2507,14 @@ sdk_methods:
   wait_policy: returns_job
   pagination_policy: none
   openapi_operation_ids: []
-  notes: 'B05 FOLDER_MOVE_NO_WAIT: SDK returns ObjectJobSchema but exposes no public wait method; do not
-    advertise --wait/--no-wait.'
+  # Internal-only: B05 FOLDER_MOVE_NO_WAIT — SDK returns ObjectJobSchema but exposes no public wait
+  # method; do not advertise --wait/--no-wait. Kept here (not in `notes`, which build_manifests.py
+  # surfaces verbatim as the agent-facing known_restrictions) per the T2-J-013 fix.
+  notes: 'Prefer dataset_ids/view_ids (the plain ids dataset get/view get return) over resource_ids
+    -- the SDK resolves them to resource ids for you. resource_ids itself takes each item''s resource
+    id, not a dataset/view''s own id. target_folder_resource_id is the destination folder''s id field,
+    exactly as folder list/folder get/folder create return it (NOT the folder''s resource_id field,
+    despite this parameter''s name).'
 - sdk_symbol: mammoth.api.folders.FoldersAPI.trash
   canonical_command: folder.trash
   alias_of: null
@@ -4185,8 +4191,9 @@ sdk_methods:
   wait_policy: returns_job
   pagination_policy: null
   openapi_operation_ids: []
-  notes: The handler enum and helper exist, but the pure contract omits it; confirm camel-case clientId
-    against the pinned server before enabling. See IO-EXPORT-HANDLERS blocker.
+  notes: Needs the Power BI account username and password, the Azure AD app's client_id, and the target
+    Power BI dataset and table; the password is a secret field, so pass it in the request file, never in
+    argv.
 - sdk_symbol: mammoth.view.ViewExport.to_redshift
   canonical_command: view.export.redshift
   alias_of: null
@@ -4281,10 +4288,8 @@ notes_on_dispositions:
   a reviewed typed fixture." No SDK method backs this handler.'
 - 'email export handler: "Outbound email stays contract-only until a dedicated sink and recipient allowlist
   exist" (acceptance class contract_only_high_impact).'
-- 'powerbi export handler: "The handler enum and helper exist, but the pure contract omits it. Confirm
-  camel-case clientId against the pinned server before enabling."'
-- 'IO-EXPORT-HANDLERS blocker: "csv_file, powerbi, and any server-rejected handler ... never infer support
-  from the enum."'
+- 'IO-EXPORT-HANDLERS blocker: "csv_file and any server-rejected handler ... never infer support from the
+  enum."'
 - 'B04 SERVER_VARIANCE (doc 09): "project browse and dashboard sources are documented as returning HTTP
   500 on some servers; schedule list may return 405. A permission or 5xx response is not server_unavailable;
   retain the live exemption evidence."'

{mammoth_cli-2.0.51 → mammoth_cli-2.0.53}/spec/manifests/sdk-methods.yaml

@@ -4130,7 +4130,7 @@ methods:
   reviewed_by: primary
 - sdk_symbol: mammoth.api.folders.FoldersAPI.move
   implementation_origin: mammoth.api.folders.FoldersAPI.move
-  signature: 'move(self, resource_ids: ''_list[str]'', target_folder_resource_id: ''str | None'' = None, source_folder_resource_id: ''str | None'' = None, workspace_id: ''int | None'' = None, project_id: ''int | None'' = None) -> ''ObjectJobSchema'''
+  signature: 'move(self, resource_ids: ''_list[str] | None'' = None, target_folder_resource_id: ''str | None'' = None, source_folder_resource_id: ''str | None'' = None, workspace_id: ''int | None'' = None, project_id: ''int | None'' = None, *, dataset_ids: ''_list[int] | None'' = None, view_ids: ''_list[int] | None'' = None) -> ''ObjectJobSchema'''
   openapi_operation_ids: []
   canonical_command: folder.move
   alias_of: null