CLI Commands
The Uniflow CLI manages the full lifecycle of your CDP deployment.
Installation
Section titled “Installation”npm install -g uniflowCommands
Section titled “Commands”uniflow init
Section titled “uniflow init”Interactive setup wizard that generates uniflow.config.yaml.
uniflow initPrompts for:
- AWS region — deployment target (e.g.
us-east-1) - Admin email — for Cognito user pool
- Retention days — S3 raw event retention (default: 90)
- Connectors — which destination connectors to enable
- Stack name — CloudFormation stack name (default:
UnifowStack)
uniflow deploy
Section titled “uniflow deploy”Deploy or update the Uniflow stack on your AWS account.
uniflow deployuniflow deploy --skip-migrations| Flag | Description |
|---|---|
--skip-migrations | Skip database migrations |
This reads uniflow.config.yaml, runs any pending migrations, and executes cdk deploy with your configuration.
uniflow status
Section titled “uniflow status”Check the health and status of your deployed stack.
uniflow statusDisplays:
- Stack status — e.g.
CREATE_COMPLETE,UPDATE_COMPLETE - Region — AWS region
- Last updated — timestamp of last deployment
- Outputs — API endpoints, CloudFront URL, etc.
Status is color-coded: green for healthy, yellow for in-progress, red for failed.
uniflow upgrade
Section titled “uniflow upgrade”Upgrade Uniflow to the latest version and redeploy.
uniflow upgradeThis command:
- Updates the
@uniflow/cdkpackage to the latest version - Runs any new migrations
- Redeploys the CDK stack
uniflow destroy
Section titled “uniflow destroy”Tear down the Uniflow stack and remove all AWS resources.
uniflow destroyuniflow destroy --force| Flag | Description |
|---|---|
-f, --force | Skip confirmation prompt |
S3 buckets with a RETAIN deletion policy are preserved even after destroy.
uniflow dev
Section titled “uniflow dev”Start a local development environment using Docker and LocalStack.
uniflow devuniflow dev --full| Flag | Description |
|---|---|
--full | Include the audience-builder container |
Prerequisites: Docker must be running.
This starts LocalStack with DynamoDB, S3, Kinesis, and SQS emulation. Outputs local endpoint URLs and resource names for testing.