[DRAFT] Tinybird TYPE ENDPOINT definitions and add missing metadata#3974
[DRAFT] Tinybird TYPE ENDPOINT definitions and add missing metadata#3974general-adhoc wants to merge 2 commits into
Conversation
|
@general-adhoc is attempting to deploy a commit to the Dub Team on Vercel. A member of the Team first needs to authorize it. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
4531568 to
b371d28
Compare
This PR has two fixes to address issues encountered during local dev onboarding:
TYPE ENDPOINTis supported by Tinybird Classic (docs link) and required by Tinybird Forward to publish a.pipeas an API endpoint. This updates existing endpoint pipes to use the explicit endpoint type while leaving materialized pipes unchanged. Classic inferred more from the workspace/UI while Forward workspaces are stricter about datafiles as source of truth.partner_tag_idsin packages/tinybird/pipes/dub_links_metadata_pipe.pipeTesting
NOTE: This was tested against a TinyBird FORWARD workspace, as I do not have the ability to create Classic workspaces. Dub's prod environment is a Classic workspace AFAIK.
Someone with access to prod TinyBird will need to run:
tb --cloud deployment create --checkdoc linkand ensure that this does not make any material changes + test these changes against a TinyBird Classic Workspace running a Dub Dev environment