tinybird-deploy

Deploy Tinybird pipes and datasources to staging and production workspaces with the Forward CLI.

5.0k|1.0k|Updated Apr 15, 2021
One-click install
npx skills add https://github.com/pollinations/pollinations --skill tinybird-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tinybird-deploy
Source: https://github.com/pollinations/pollinations/tree/main/.claude/skills/tinybird-deploy
Command: npx skills add https://github.com/pollinations/pollinations --skill tinybird-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying Tinybird observability pipes and datasources across staging and production workspaces is error-prone: wrong CLI versions, wrong workspace tokens, and accidental destructive operations can break analytics pipelines. This Skill enforces a safe, repeatable deployment workflow for the enter.pollinations.ai observability stack.

Core Features & Use Cases

  • Safe Deployment Workflow: Validate with a dry run, deploy to staging, verify endpoints, then promote to production only on explicit request.
  • Workspace & Token Discipline: Route deployments to the correct workspace (pollinations_enter or pollinations_enter_staging) using scoped deploy tokens pulled from the macOS Keychain.
  • Troubleshooting Guidance: Resolve Forward vs Classic CLI conflicts, pipe timeouts, materialized view validation failures, and accidental datasource deletion prompts.
  • Use Case: After editing a .pipe file like weekly_usage_stats.pipe, run a checked deployment to staging, verify the endpoint returns data, then deploy to production when asked.

Quick Start

Deploy my updated Tinybird pipes to the staging workspace and verify the weekly_usage_stats endpoint returns data.

Frequently Asked Questions about tinybird-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Tinybird pipes to production safely?

Deploy Tinybird pipes by first running a dry run with tb --cloud deployment create --check, then deploying to staging with --wait, verifying endpoints, and only deploying to production after explicit approval. Never pass --auto or --allow-destructive-operations unless requested.

How do I deploy to multiple Tinybird workspaces with one CLI?

Use workspace-scoped tokens with the same regional host, since the token selects the workspace. Set TB_TOKEN to a staging deploy token for pollinations_enter_staging or a prod deploy token for pollinations_enter, and pass --host on every command.

Tinybird Forward CLI vs Classic CLI: which should I use?

Use the Forward CLI (tb at ~/.local/bin/tb) for deployment create workflows. The Classic CLI installed via pip install tinybird-cli does not support Forward workspaces and should only remain available as tb-classic.

Why does Tinybird validation report datasource deletion?

Validation reports deletion when a datasource exists remotely but is missing from your local definitions. Stop immediately, do not rerun with --allow-destructive-operations, and either restore the local definition or ask before deleting anything.

How do I fix Tinybird pipe timeout issues with large date ranges?

Fix pipe timeouts by using uniq() instead of uniqExact() for user counts, avoiding CTE plus JOIN patterns in favor of single-pass queries, and considering materialized views for expensive aggregations.