fix(ci): deploy Tinybird Forward resource token scopes - #533
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 5790fe4. Configure here.
Summary
Production delivery provisioning failed with HTTP 403 because Tinybird Forward manages resource-scoped tokens through datafile deployment. The workflow attempted to create those tokens through the Token API.
Declare all 41 permissions for the three Worker tokens in the generated deployment tree. Preserve legacy datasource definitions while adding the exact append-token directive. Repeated expansion accepts existing identical declarations. The provisioning step now reads deployed tokens, verifies exact scopes, and exports them without API mutations.
Validation
844d8f03: valid, exactly three tokens created with 41 added scopes, no removed permissions or resource deletions.5790fe4d14294ebcd42bd25d367c27042d64be42with no findings. Current-head hosted CI passed.Risk
HIGH: production schema deployment and credential provisioning. The existing operator and deploy credentials stay separate. No runtime permission is broadened beyond the previously reviewed three token definitions. Cloud apply is performed by Actions after merge.
TRA-276. Follows #531 and #532.
Tinybird Forward resource-token contract.