Skip to content

chore: migrate CFA Tinybird workspace from Classic to Forward - #71

Open
VinneyJ wants to merge 6 commits into
chore/sync-upstream-aug-2026from
chore/tinybird-cfa-config-v2
Open

chore: migrate CFA Tinybird workspace from Classic to Forward#71
VinneyJ wants to merge 6 commits into
chore/sync-upstream-aug-2026from
chore/tinybird-cfa-config-v2

Conversation

@VinneyJ

@VinneyJ VinneyJ commented Aug 13, 2026

Copy link
Copy Markdown

Summary

Migrates the CFA Tinybird workspace from the Classic deployment model to Forward. This is a CFA-specific configuration change — the upstream dubinc/dub workspace is managed separately and unaffected.

  • Migrated datasources and pipes from Classic to Forward format
  • Added v2 endpoint pipes so Forward exposes them as HTTP endpoints
  • Removed FORWARD_QUERY blocks from datasources (not needed in Forward)
  • Cleaned up scripts/ directory (not applicable to Forward workspaces)

Base

Stacked on #70 (upstream sync). Targeting chore/sync-upstream-aug-2026 — will retarget to main once #70 merges.

What changed

Only packages/tinybird/ files. No app code, no schema, no dependencies touched.

- Add FORWARD_QUERY directives to datasources with schema changes
  (dub_click_events, dub_sale_events, dub_lead_events,
   dub_api_logs, dub_links_metadata)
- Add partner_tag_ids to dub_links_metadata_pipe explicit column list
- Add dub_regular_links_metadata_latest datasource and materialization
- Add v2 endpoint pipes from Classic workspace (endpoints/ directory)
- Add tinybird.config.json for Forward workspace configuration
- Add backup script for pre-migration data export
@vercel

vercel Bot commented Aug 13, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
dub Error Error Aug 13, 2026 2:12pm

Request Review

@maquchizi

Copy link
Copy Markdown

@VinneyJ Once #70 is merged, I suggest that you don't merge these changes into main. Instead, you should:

  1. Create a new branch from main
  2. Merge these changes into that branch
  3. Set that branch to track the upstream main
  4. Set that branch as the default branch for this fork

That way, we'll avoid this situation happening again and syncing with upstream will literally be just clicking a button.

@VinneyJ

VinneyJ commented Aug 13, 2026

Copy link
Copy Markdown
Author

Thanks, @maquchizi. This is very useful information. We will be using this approach going forward. Setting that up in a few.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants