chore: migrate Tinybird workspace from Classic to Forward - #68
Open
VinneyJ wants to merge 5 commits into
Open
Conversation
- 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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tinybird.config.jsonrequired by Tinybird ForwardTYPE endpointto v4 analytics pipes so Forward exposes them as HTTP endpointsFORWARD_QUERYblocks after migration completed (they were one-time migration artifacts)pipes/to match upstream structureWhy this is separate from the upstream sync
This is a CFA infrastructure change, not an upstream code change. Upstream manages their own Tinybird workspace separately and is unaffected by this.
Test plan