You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ODS CLI: **`b2c sandbox create`** adds **`--emails`** for notification addresses; **`b2c sandbox update`** adds **`--start-scheduler`**, **`--stop-scheduler`**, **`--clear-start-scheduler`**, and **`--clear-stop-scheduler`**; **`b2c realm update`** adds **`--emails`**, **`--start-scheduler`**, **`--stop-scheduler`**, **`--clear-start-scheduler`**, and **`--clear-stop-scheduler`**.
7
+
8
+
Sandbox API: **`b2c sandbox operations list`** and **`b2c sandbox operations get`** (inspect lifecycle operations); **`b2c sandbox alias get`** (get one alias by ID, same endpoint as **`alias list --alias-id`**).
9
+
10
+
User guide updated for scheduling flags, sandbox operations, and **`b2c sandbox alias get`**.
Copy file name to clipboardExpand all lines: docs/cli/sandbox.md
+151-1Lines changed: 151 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ These commands were previously available as `b2c ods <command>`. The `ods` prefi
12
12
13
13
## Sandbox ID Formats
14
14
15
-
Commands that operate on a specific sandbox (`get`, `update`, `start`, `stop`, `restart`, `delete`) accept two ID formats:
15
+
Commands that operate on a specific sandbox (`get`, `update`, `start`, `stop`, `restart`, `delete`, `operations list`, `operations get`) accept two ID formats:
## b2c sandbox operations list {#b2c-sandbox-operations-list}
396
+
397
+
List past and current **operations** on a sandbox (for example start, stop, restart, reset, create, delete, upgrade). This maps to the ODS API `GET /sandboxes/{sandboxId}/operations` endpoint.
398
+
399
+
To **request** a lifecycle operation (`start`, `stop`, `restart`, `reset`), use `b2c sandbox start|stop|restart|reset` instead; those commands call `POST /sandboxes/{sandboxId}/operations`.
400
+
401
+
### Usage
402
+
403
+
```bash
404
+
b2c sandbox operations list <SANDBOXID>
405
+
```
406
+
407
+
### Arguments
408
+
409
+
| Argument | Description | Required |
410
+
|----------|-------------|----------|
411
+
|`SANDBOXID`| Sandbox ID (UUID or realm-instance, e.g., `zzzv-123`) | Yes |
412
+
413
+
### Flags
414
+
415
+
| Flag | Short | Description | Default |
416
+
|------|-------|-------------|---------|
417
+
|`--from`|| Earliest operation time (ISO 8601). If omitted, the API defaults to roughly the last 30 days. ||
418
+
|`--to`|| Latest operation time (ISO 8601). If omitted, the API defaults to now. ||
419
+
|`--operation-state`|| Filter by lifecycle state: `pending`, `running`, or `finished`||
420
+
|`--status`|| Filter finished operations by outcome: `success` or `failure`||
b2c sandbox operations list zzzv-123 --columns operation,operationState,status,createdAt
449
+
450
+
# Full API response (includes paging metadata when present)
451
+
b2c sandbox operations list zzzv-123 --json
452
+
```
453
+
454
+
### Output
455
+
456
+
When not using `--json`, the command prints a one-line paging summary when metadata is present, then a table of operations. Use `--json` to inspect `metadata` (page, totals) and the raw `data` array.
457
+
458
+
---
459
+
460
+
## b2c sandbox operations get {#b2c-sandbox-operations-get}
461
+
462
+
Return details for a **single** sandbox operation by its operation UUID (maps to `GET /sandboxes/{sandboxId}/operations/{operationId}`). Use the operation `id` from `b2c sandbox operations list` or from the JSON output of `b2c sandbox start|stop|restart|reset` when using `--json`.
463
+
464
+
### Usage
465
+
466
+
```bash
467
+
b2c sandbox operations get <SANDBOXID><OPERATIONID>
468
+
```
469
+
470
+
### Arguments
471
+
472
+
| Argument | Description | Required |
473
+
|----------|-------------|----------|
474
+
|`SANDBOXID`| Sandbox ID (UUID or realm-instance, e.g., `zzzv-123`) | Yes |
475
+
|`OPERATIONID`| Operation UUID | Yes |
476
+
477
+
### Examples
478
+
479
+
```bash
480
+
# Show operation details (human-readable)
481
+
b2c sandbox operations get zzzv-123 550e8400-e29b-41d4-a716-446655440000
482
+
483
+
# Operation as JSON (sandbox operation model only)
484
+
b2c sandbox operations get zzzv-123 550e8400-e29b-41d4-a716-446655440000 --json
485
+
```
486
+
487
+
### Output
488
+
489
+
When not using `--json`, the command prints a short **Operation Details** block including operation type, state, outcome, sandbox state, created time, and who ran the operation when available.
490
+
491
+
With `--json`, the command returns the **operation object** (not the full API envelope), consistent with `b2c sandbox get`.
- The `--ttl` value is added to the existing sandbox lifetime, not an absolute value. Together with previous extensions, it must adhere to the realm's maximum TTL configuration.
553
662
- Setting `--ttl` to 0 or less gives the sandbox an infinite lifetime (subject to realm configuration).
663
+
-`--auto-scheduled` controls whether automatic start/stop behavior is enabled for the sandbox.
664
+
-`--start-scheduler` and `--stop-scheduler` define scheduler values, but scheduler automation is effective only when `--auto-scheduled` is enabled.
554
665
555
666
---
556
667
@@ -685,6 +796,7 @@ Alias commands are available both under the `sandbox` topic and the legacy `ods`
685
796
686
797
-`b2c sandbox alias create`
687
798
-`b2c sandbox alias list`
799
+
-`b2c sandbox alias get`
688
800
-`b2c sandbox alias delete`
689
801
690
802
### b2c sandbox alias create
@@ -779,6 +891,39 @@ When listing multiple aliases without `--json`, the command prints a table with:
779
891
- Whether the alias is unique
780
892
- DNS verification record (if any)
781
893
894
+
For **one alias** by ID, you can also use **`b2c sandbox alias get`** (same API as `list --alias-id`).
895
+
896
+
### b2c sandbox alias get {#b2c-sandbox-alias-get}
897
+
898
+
Get details for a **single** hostname alias (ODS API `GET /sandboxes/{sandboxId}/aliases/{sandboxAliasId}`). This is equivalent to `b2c sandbox alias list <SANDBOXID> --alias-id <ALIASID>` but uses positional arguments only.
899
+
900
+
#### Usage
901
+
902
+
```bash
903
+
b2c sandbox alias get <SANDBOXID><ALIASID>
904
+
```
905
+
906
+
#### Arguments
907
+
908
+
| Argument | Description | Required |
909
+
|----------|-------------|----------|
910
+
|`SANDBOXID`| Sandbox ID (UUID or realm-instance, e.g., `zzzv-123`) | Yes |
911
+
|`ALIASID`| Alias UUID | Yes |
912
+
913
+
#### Examples
914
+
915
+
```bash
916
+
# Human-readable details
917
+
b2c sandbox alias get zzzv-123 some-alias-uuid
918
+
919
+
# Alias object as JSON (same shape as list/get for a single alias)
920
+
b2c sandbox alias get zzzv-123 some-alias-uuid --json
921
+
```
922
+
923
+
#### Output
924
+
925
+
When not using `--json`, the command prints an **Alias Details** section (hostname, status, uniqueness, DNS TXT verification, registration URL when present, optional cookie hint). With `--json`, it returns the **alias object** only.
0 commit comments