Deploying a Bridge
Once your bridge is built and tested, deploy it to make it available in the portal.
Using the CLI
From the hub/ directory:
pnpm orderly bridge deploy -n my-platformThis command:
- Validates the bridge manifest
- Builds the bridge package
- Registers the bridge type in the
bridge_typestable - Makes it available for users to configure in the portal
Deploy Options
pnpm orderly bridge deploy [options]| Option | Description |
|---|---|
-n, --name <name> | Bridge package name (required) |
--dry-run | Validate without deploying |
--force | Overwrite existing bridge type |
What Happens During Deploy
- Validation — The CLI reads your bridge’s manifest and validates all required fields, task names, and config field types
- Build — The bridge package is compiled with
tsup - Registration — A row is inserted/updated in
bridge_typeswith the manifest data - Availability — Users can now see and configure this bridge in Bridges > Add Bridge
Listing Deployed Bridges
pnpm orderly bridge listThis shows all registered bridge types grouped by category.
Updating a Bridge
To deploy a new version, increment the version field in your manifest and run deploy again:
pnpm orderly bridge deploy -n my-platformExisting bridge instances will continue using their current configuration. New instances will use the updated manifest.
Validating Without Deploying
pnpm orderly bridge deploy -n my-platform --dry-runThis checks for:
- Valid manifest structure
- All required tasks for the category are present
- Config fields have correct types
- Auth methods are properly declared