bt-cli 0.4.35__tar.gz → 0.4.36__tar.gz

{bt_cli-0.4.35/src/bt_cli/data → bt_cli-0.4.36/.claude}/skills/epml/SKILL.md

@@ -205,6 +205,26 @@ bt epml quick tests-then-deploy --suite <suite_id>      # commits if pass; rollb
 
 - **`bt epml rbp roles get <id>`** — there is no GET-single-role in the v1 API. The detailed view (role with all child relations resolved) only exists at `/api/v6/pbul/{hostid}/rbp/roledetail/{id}`, which is on the IAM-only authorizer. Not callable with a PAT today. Workaround: use `bt epml rbp roles list` for the role row, then `bt epml rbp roles {cmdgrps,hostgrps,usergrps,tmdategrps} list <id>` to fetch each child relation.
 
+## Tenant-side gotchas (not a CLI bug)
+
+- **`bt epml rbp tx begin` may return** `400 "RBP Transactions not enabled on host"`. This is a per-tenant feature flag on the PMUL host — transactions need to be enabled at the appliance / settings level before they'll work. The CLI surfaces the server's exact message; nothing client-side to fix. (Verified 2026-05-01 against the lab tenant — host id 100 does not have transactions enabled.) The `quick tests-then-deploy` workflow depends on transactions, so it'll also fail until the host is configured for it.
+
+## tmdate shape (`dotw` map)
+
+The OpenAPI spec describes `tmdate` as a `string` field with `x-go-name: "JsonDefinition"`. The actual runtime shape is a structured object:
+
+```json
+{"dotw": {
+  "mon": [{"from":"09:00","to":"17:00"}],
+  "tue": [{"from":"09:00","to":"17:00"}],
+  ...
+  "sat": [],
+  "sun": []
+}}
+```
+
+A day with an empty list is inactive. A day can have multiple windows (e.g. split shift). The CLI's `--from/--to/--days` short flags build the map for you; for anything more complex use `--file` with the full JSON.
+
 ## Path-version policy (CLI internal)
 
 Where the spec offers both legacy `/api/pbul/{hostid}/rbp/<x>` and newer

{bt_cli-0.4.35 → bt_cli-0.4.36}/CLAUDE.md

@@ -1,6 +1,6 @@
 # BT-CLI
 
-BeyondTrust Platform CLI for Password Safe, Entitle, PRA, EPM Windows, and EPM Linux. **Version: 0.4.35**
+BeyondTrust Platform CLI for Password Safe, Entitle, PRA, EPM Windows, and EPM Linux. **Version: 0.4.36**
 
 ## Setup
 

{bt_cli-0.4.35 → bt_cli-0.4.36}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: bt-cli
-Version: 0.4.35
+Version: 0.4.36
 Summary: BeyondTrust Platform CLI (unofficial) - Password Safe, Entitle, PRA, EPM
 Author-email: Dave Grendysz <dgrendysz@beyondtrust.com>
 License: MIT

{bt_cli-0.4.35 → bt_cli-0.4.36}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "bt-cli"
-version = "0.4.35"
+version = "0.4.36"
 description = "BeyondTrust Platform CLI (unofficial) - Password Safe, Entitle, PRA, EPM"
 readme = "README.md"
 requires-python = ">=3.9"

{bt_cli-0.4.35 → bt_cli-0.4.36}/src/bt_cli/__init__.py

@@ -1,3 +1,3 @@
 """BeyondTrust Unified Admin CLI."""
 
-__version__ = "0.4.35"
+__version__ = "0.4.36"

{bt_cli-0.4.35 → bt_cli-0.4.36}/src/bt_cli/data/CLAUDE.md

@@ -1,6 +1,6 @@
 # BT-CLI
 
-BeyondTrust Platform CLI for Password Safe, Entitle, PRA, EPM Windows, and EPM Linux. **Version: 0.4.35**
+BeyondTrust Platform CLI for Password Safe, Entitle, PRA, EPM Windows, and EPM Linux. **Version: 0.4.36**
 
 ## Setup
 

{bt_cli-0.4.35/.claude → bt_cli-0.4.36/src/bt_cli/data}/skills/epml/SKILL.md

@@ -205,6 +205,26 @@ bt epml quick tests-then-deploy --suite <suite_id>      # commits if pass; rollb
 
 - **`bt epml rbp roles get <id>`** — there is no GET-single-role in the v1 API. The detailed view (role with all child relations resolved) only exists at `/api/v6/pbul/{hostid}/rbp/roledetail/{id}`, which is on the IAM-only authorizer. Not callable with a PAT today. Workaround: use `bt epml rbp roles list` for the role row, then `bt epml rbp roles {cmdgrps,hostgrps,usergrps,tmdategrps} list <id>` to fetch each child relation.
 
+## Tenant-side gotchas (not a CLI bug)
+
+- **`bt epml rbp tx begin` may return** `400 "RBP Transactions not enabled on host"`. This is a per-tenant feature flag on the PMUL host — transactions need to be enabled at the appliance / settings level before they'll work. The CLI surfaces the server's exact message; nothing client-side to fix. (Verified 2026-05-01 against the lab tenant — host id 100 does not have transactions enabled.) The `quick tests-then-deploy` workflow depends on transactions, so it'll also fail until the host is configured for it.
+
+## tmdate shape (`dotw` map)
+
+The OpenAPI spec describes `tmdate` as a `string` field with `x-go-name: "JsonDefinition"`. The actual runtime shape is a structured object:
+
+```json
+{"dotw": {
+  "mon": [{"from":"09:00","to":"17:00"}],
+  "tue": [{"from":"09:00","to":"17:00"}],
+  ...
+  "sat": [],
+  "sun": []
+}}
+```
+
+A day with an empty list is inactive. A day can have multiple windows (e.g. split shift). The CLI's `--from/--to/--days` short flags build the map for you; for anything more complex use `--file` with the full JSON.
+
 ## Path-version policy (CLI internal)
 
 Where the spec offers both legacy `/api/pbul/{hostid}/rbp/<x>` and newer

{bt_cli-0.4.35 → bt_cli-0.4.36}/src/bt_cli/epml/commands/rbp_tmdategrps.py

@@ -95,7 +95,12 @@ def list_tmdates(
     host: Optional[int] = _host_opt(),
     output: OutputFormat = typer.Option(OutputFormat.JSON, "--output", "-o"),
 ):
-    """List time/date entries in a group."""
+    """List time/date entries in a group.
+
+    Each entry's schedule lives in the nested `dotw` map. Defaults to JSON
+    output because the structure is non-tabular; use `-o table` for a
+    summarized day-by-day view.
+    """
     from bt_cli.epml.client import get_client
     try:
         with get_client() as c:
@@ -104,10 +109,26 @@ def list_tmdates(
             print_json(data)
         else:
             rows = data if isinstance(data, list) else (data.get("data", []) if isinstance(data, dict) else [])
-            print_table(rows, [
-                ("ID", "id"),
+            view = []
+            for r in rows:
+                dotw = (r.get("dotw") or {})
+                active_days = [d for d in ("mon","tue","wed","thu","fri","sat","sun") if dotw.get(d)]
+                # Show window summary using the first day's first window if any
+                window = ""
+                for d in active_days:
+                    rng = (dotw.get(d) or [{}])[0]
+                    if rng.get("from") and rng.get("to"):
+                        window = f"{rng['from']}-{rng['to']}"
+                        break
+                view.append({
+                    "description": r.get("description", "") or r.get("name", "") or "-",
+                    "days": ",".join(active_days) or "-",
+                    "window": window or "-",
+                })
+            print_table(view, [
                 ("Description", "description"),
-                ("Disabled", "disabled"),
+                ("Days", "days"),
+                ("Window", "window"),
             ], title=f"tmdates in tmdategrp {tmdategrp_id}")
     except httpx.HTTPStatusError as e:
         print_api_error(e, "list tmdates"); raise typer.Exit(1)
@@ -115,18 +136,46 @@ def list_tmdates(
         print_api_error(e, "list tmdates"); raise typer.Exit(1)
 
 
+_VALID_DAYS = ("mon", "tue", "wed", "thu", "fri", "sat", "sun")
+
+
+def _build_dotw(from_: str, to: str, days: str) -> dict:
+    """Build a `dotw` map (day-of-the-week → list of from/to ranges).
+
+    The spec calls the per-tmdate field `tmdate: string` (a JSON definition)
+    but the actual API uses a structured object: `{"dotw": {"mon": [{"from":"...","to":"..."}], ...}}`.
+    Days that aren't in `--days` get an empty list (= not active).
+    """
+    selected = {d.strip().lower() for d in days.split(",") if d.strip()}
+    bad = selected - set(_VALID_DAYS)
+    if bad:
+        raise ValueError(f"unknown days: {','.join(sorted(bad))} — must be in {','.join(_VALID_DAYS)}")
+    window = {"from": from_, "to": to}
+    return {d: ([window] if d in selected else []) for d in _VALID_DAYS}
+
+
 @tmdates_app.command("add")
 def add_tmdates(
     tmdategrp_id: int = typer.Argument(..., help="Time/Date group ID"),
-    file: Optional[typer.FileText] = typer.Option(None, "--file", "-f", help="JSON file: array of tmdate objects"),
+    file: Optional[typer.FileText] = typer.Option(None, "--file", "-f", help="JSON file: array of tmdate objects (full shape, with `dotw`)"),
     description: Optional[str] = typer.Option(None, "--description", "-d", help="Description for a single tmdate (used with --from/--to)"),
     from_: Optional[str] = typer.Option(None, "--from", help="Time window start (e.g. 09:00)"),
     to: Optional[str] = typer.Option(None, "--to", help="Time window end (e.g. 17:00)"),
+    days: str = typer.Option("mon,tue,wed,thu,fri", "--days", help="Comma-separated days when --from/--to applies"),
     host: Optional[int] = _host_opt(),
 ):
-    """Add tmdate entries. Provide --file for full bodies, or --from/--to/--description for one quick entry.
+    """Add tmdate entries.
 
-    The API wraps the body as `{"tmdates": [...]}` (the spec doesn't document this).
+    Two ways to specify entries:
+
+    - **--from / --to / --days**: quick one-window helper. Builds a per-day-of-week
+      schedule (`dotw` map). Default `--days mon,tue,wed,thu,fri` (weekdays).
+    - **--file**: a JSON array of full tmdate objects. Each object should be
+      `{"dotw": {"mon": [{"from":"09:00","to":"17:00"}], ...}}` — every weekday key
+      with a list of windows. Days you omit are silently treated as inactive.
+
+    The wrapper around the array (`{"tmdates": [...]}`) is added by the client
+    automatically — it's not in the spec but is required by the server.
     """
     from bt_cli.epml.client import get_client
     if file:
@@ -136,9 +185,13 @@ def add_tmdates(
             raise typer.Exit(2)
     else:
         if not (from_ and to):
-            typer.echo("Provide --file, or both --from and --to (with optional --description)", err=True)
+            typer.echo("Provide --file, or both --from and --to (with optional --description / --days)", err=True)
+            raise typer.Exit(2)
+        try:
+            entry = {"dotw": _build_dotw(from_, to, days)}
+        except ValueError as e:
+            typer.echo(f"Bad --days: {e}", err=True)
             raise typer.Exit(2)
-        entry = {"from": from_, "to": to}
         if description:
             entry["description"] = description
         tmdates = [entry]