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
Add support for realm-instance format in ODS commands. You can now use `zzzv-123` or `zzzv_123` instead of full UUIDs for `ods get`, `ods start`, `ods stop`, `ods restart`, and `ods delete` commands.
Copy file name to clipboardExpand all lines: docs/cli/ods.md
+47-15Lines changed: 47 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,23 @@ description: Commands for creating, managing, starting, stopping, and deleting O
6
6
7
7
Commands for managing On-Demand Sandboxes (ODS).
8
8
9
+
## Sandbox ID Formats
10
+
11
+
Commands that operate on a specific sandbox (`get`, `start`, `stop`, `restart`, `delete`) accept two ID formats:
12
+
13
+
| Format | Example | Description |
14
+
|--------|---------|-------------|
15
+
| UUID |`abc12345-1234-1234-1234-abc123456789`| Full sandbox UUID |
16
+
| Realm-instance |`zzzv-123` or `zzzv_123`| Realm-instance format |
17
+
18
+
The realm-instance format uses the 4-character realm code followed by a dash (`-`) or underscore (`_`) and the instance identifier. When using the realm-instance format, the CLI automatically looks up the corresponding sandbox UUID.
19
+
20
+
```bash
21
+
# These are equivalent (assuming zzzv-123 resolves to the UUID)
22
+
b2c ods get abc12345-1234-1234-1234-abc123456789
23
+
b2c ods get zzzv-123
24
+
```
25
+
9
26
## Global ODS Flags
10
27
11
28
These flags are available on all ODS commands:
@@ -176,16 +193,19 @@ b2c ods get <SANDBOXID>
176
193
177
194
| Argument | Description | Required |
178
195
|----------|-------------|----------|
179
-
|`SANDBOXID`| Sandbox ID (UUID) | Yes |
196
+
|`SANDBOXID`| Sandbox ID (UUID or realm-instance, e.g., `zzzv-123`) | Yes |
180
197
181
198
### Examples
182
199
183
200
```bash
184
-
# Get sandbox details
201
+
# Get sandbox details using UUID
185
202
b2c ods get abc12345-1234-1234-1234-abc123456789
186
203
204
+
# Get sandbox details using realm-instance format
205
+
b2c ods get zzzv-123
206
+
187
207
# Output as JSON
188
-
b2c ods get abc12345-1234-1234-1234-abc123456789 --json
208
+
b2c ods get zzzv_123 --json
189
209
```
190
210
191
211
### Output
@@ -244,16 +264,19 @@ b2c ods start <SANDBOXID>
244
264
245
265
| Argument | Description | Required |
246
266
|----------|-------------|----------|
247
-
|`SANDBOXID`| Sandbox ID (UUID) | Yes |
267
+
|`SANDBOXID`| Sandbox ID (UUID or realm-instance, e.g., `zzzv-123`) | Yes |
Copy file name to clipboardExpand all lines: docs/guide/configuration.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,6 +69,21 @@ You can configure the CLI using environment variables:
69
69
|`SFCC_OAUTH_SCOPES`| OAuth scopes to request |
70
70
|`SFCC_CODE_VERSION`| Code version for deployments |
71
71
72
+
## .env File
73
+
74
+
The CLI automatically loads a `.env` file from the current working directory if present. Use the same `SFCC_*` variable names as environment variables.
Add `.env` to your `.gitignore` to avoid committing credentials.
85
+
:::
86
+
72
87
## Configuration File
73
88
74
89
You can create a `dw.json` file to store instance settings. The CLI searches for this file starting from the current directory and walking up the directory tree.
@@ -189,7 +204,7 @@ Sensitive fields like `hostname`, `password`, `clientSecret`, `username`, and `m
189
204
190
205
Configuration is resolved with the following precedence (highest to lowest):
191
206
192
-
1.**CLI flags and environment variables** - Explicit values always take priority
207
+
1.**CLI flags and environment variables** - Explicit values always take priority (includes `.env` file)
0 commit comments