static-content
static-content component
Get a custom component as raw JavaScript
Usage
bash
pega static-content component <componentID> [flags]Source endpoint: GET /components/{componentID} — view command source
Arguments
| Argument | Required | Description |
|---|---|---|
componentID | Yes | Component ID |
Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--format | option | No | json | Output format (json, compact, yaml, table) |
--fields | option | No | Comma-separated top-level fields to include in output | |
--dry-run | boolean | No | Print HTTP request details and exit without executing | |
--quiet | boolean | No | Suppress all stderr progress/warning output | |
--verbose | boolean | No | Emit full HTTP request/response details to stderr | |
--no-cache | boolean | No | Bypass token file cache; perform fresh OAuth exchange | |
--profile | option | No | default | Named config profile |
-o, --output | option | No | Write component JS to this file path (default: stdout) |
Examples
sh
pega static-content component MyComponentsh
pega static-content component MyComponent --output ./my-component.jsstatic-content file
Get a static file (binary). --output is required.
Usage
bash
pega static-content file <fileID> [flags]Source endpoint: GET /files/{fileID} — view command source
Arguments
| Argument | Required | Description |
|---|---|---|
fileID | Yes | File ID |
Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--format | option | No | json | Output format (json, compact, yaml, table) |
--fields | option | No | Comma-separated top-level fields to include in output | |
--dry-run | boolean | No | Print HTTP request details and exit without executing | |
--quiet | boolean | No | Suppress all stderr progress/warning output | |
--verbose | boolean | No | Emit full HTTP request/response details to stderr | |
--no-cache | boolean | No | Bypass token file cache; perform fresh OAuth exchange | |
--profile | option | No | default | Named config profile |
-o, --output | option | Yes | Required: write binary bytes to this file path |
Examples
sh
pega static-content file MyFile --output ./my-file.binstatic-content profile-image
Get a user profile image
Usage
bash
pega static-content profile-image <userId> [flags]Source endpoint: GET /users/{user_ID}/profile-image — view command source
Arguments
| Argument | Required | Description |
|---|---|---|
userId | Yes | User ID |
Flags
| Flag | Type | Required | Default | Description |
|---|---|---|---|---|
--format | option | No | json | Output format (json, compact, yaml, table) |
--fields | option | No | Comma-separated top-level fields to include in output | |
--dry-run | boolean | No | Print HTTP request details and exit without executing | |
--quiet | boolean | No | Suppress all stderr progress/warning output | |
--verbose | boolean | No | Emit full HTTP request/response details to stderr | |
--no-cache | boolean | No | Bypass token file cache; perform fresh OAuth exchange | |
--profile | option | No | default | Named config profile |
-o, --output | option | No | Write image to this file path (default: stdout) |
Examples
sh
pega static-content profile-image user123sh
pega static-content profile-image user123 --output ./profile.jpg