Pipeline management
Apply a pipeline
Deploy a pipeline from a YAML configuration file:- Validate your pipeline configuration
- Create or update the pipeline in your current project
- Start processing data according to your configuration
Options
| Flag | Description |
|---|---|
-i, --inspect | Open the inspect TUI after successful deployment to monitor live data |
List pipelines
View all pipelines in your current project:Delete a pipeline
Remove a pipeline by name:Validate a pipeline
Check your pipeline configuration without deploying:- Catching syntax errors before deployment
- Verifying source and sink configurations
- Testing transform logic
Pause a pipeline
Temporarily stop a running pipeline:Resume a pipeline
Resume a previously paused pipeline:- For deployments: restores the replica count from the original pipeline configuration (defaults to 1 if not specified)
- For jobs: sets
suspendtofalse
You can only resume a paused pipeline. Attempting to resume an already running pipeline will return an error.
Restart a pipeline
Restart a running or paused pipeline by triggering a pod restart:Options
| Flag | Description |
|---|---|
--clear-state | Clear all state data to start processing from the beginning (default: false) |
Restart vs Resume: Use
resume to restore a paused pipeline without restarting pods. Use restart when you need to trigger a fresh pod restart, such as after configuration changes or to recover from issues. The --clear-state flag allows you to discard all checkpoints and reprocess data from the beginning.Viewing logs
Monitor your pipeline’s execution with the logs command:Inspecting live data
Open an interactive TUI to view live data flowing through your pipeline:Options
| Flag | Description |
|---|---|
-n, --topology-node-keys | Comma-separated list of nodes to filter |
-b, --buffer-size | Maximum records to keep in buffer (default: 10000) |
Keyboard shortcuts
| Key | Action |
|---|---|
Tab / ← → | Switch between topology node tabs |
j k / ↑ ↓ | Scroll up/down |
g / G | Jump to top/bottom |
/ | Search records |
n / N | Next/previous search match |
d | Toggle pipeline definition view |
w | Open in web dashboard |
q | Quit |
For detailed information about Live Inspect, including all keyboard shortcuts and features, see the Live Inspect guide.
Managing projects and secrets
The Turbo Pipelines CLI integrates with the Goldsky CLI for project managementProjects
golsky login command
Secrets
Secrets are used to store sensitive configuration like database credentials:Secrets are referenced in your pipeline YAML using the
secret_name field. See the Pipeline Configuration guide for examples.