Reactors
Commands for managing Reactors.
List Reactors
bt reactors
Lists all Reactors in your tenant with pagination. When run interactively, selecting a Reactor provides options to view details, stream logs, or delete.
Flags
| Flag | Short | Type | Default | Description |
|---|---|---|---|---|
--management-key | -x | string | BT_MANAGEMENT_KEY env var | Management API key |
--page | -p | integer | 1 | Page number to fetch |
Required Permissions
reactor:read
Example
bt reactors -p 2
Create Reactor
bt reactors create
Creates a new Reactor. When flags are omitted, the CLI will interactively prompt for required values.
Flags
Basic
| Flag | Short | Type | Default | Description |
|---|---|---|---|---|
--management-key | -x | string | BT_MANAGEMENT_KEY env var | Management API key |
--name | -n | string | (prompted) | Name of the Reactor |
--code | -r | file path | (prompted) | Path to JavaScript file containing reactor code |
--application-id | -i | string | — | Optional Application ID. Only supported for the node-bt runtime. |
--configuration | -c | file path | — | Path to .env format configuration file |
Runtime
The
node-bt runtime is deprecated. Use a Node.js runtime image for new Reactors and Proxy code transforms. Migrate away from the node-bt runtime as soon as possible to avoid disruption.| Flag | Type | Default | Description |
|---|---|---|---|
--image | string | None | Runtime image. If omitted, the CLI prompts you to select one. Use a Node.js runtime image for new Reactors. |
--timeout | integer | 10 | Timeout in seconds, 10 to 900 (Node.js runtime images only; maximum 30 when runtime async is disabled) |
--warm-concurrency | integer | 0 | Number of warm instances. The default quota is 0 for Test tenants and 1 for Production tenants. Request a higher quota if needed. (Node.js runtime images only) |
--resources | string | standard | Resource tier: standard, large, xlarge (Node.js runtime images only) |
--package-json | file path | - | Path to a package.json file specifying dependencies (Node.js runtime images only) |
--permissions | string[] | — | Permission grants, repeatable (Node.js runtime images only) |
--[no-]async | boolean | false | Enable or disable asynchronous Reactor execution (Node.js runtime images only) |
Advanced
| Flag | Type | Default | Description |
|---|---|---|---|
--no-wait | boolean | false | Don't wait for Reactor provisioning to complete |
--async configures asynchronous Reactor execution. It is independent from --no-wait, which controls whether the CLI waits for provisioning.Required Permissions
reactor:create
Examples
Create a Reactor with the node24 runtime image:
bt reactors create \
-n "My Reactor" \
-r ./reactor.js \
--image node24 \
--package-json ./package.json \
--timeout 20 \
--permissions "token:read" \
--permissions "token:create"
Create an asynchronous Reactor with the node24 runtime image:
bt reactors create \
-n "My Async Reactor" \
-r ./reactor.js \
--image node24 \
--async \
--timeout 900
Create a Reactor with the deprecated node-bt runtime:
bt reactors create \
-n "My Reactor" \
-r ./reactor.js \
-i "your-application-id" \
--image node-bt
Update Reactor
bt reactors update <id>
Updates an existing Reactor.
Arguments
| Argument | Required | Description |
|---|---|---|
id | Yes | The Reactor ID to update |
Flags
All flags from Create Reactor, plus:
| Flag | Short | Type | Default | Description |
|---|---|---|---|---|
--watch | -w | boolean | false | Watch code and configuration files for changes and auto-update |
--logs | -l | boolean | false | Stream logs after update |
The
--watch flag monitors your code and configuration files for changes, automatically redeploying when files are saved. This is useful during development.Required Permissions
reactor:update