feat(webapp): add RUNTIME_API_ORIGIN to decouple runner traffic from external origin - #4435
feat(webapp): add RUNTIME_API_ORIGIN to decouple runner traffic from external origin#4435deepshekhardas wants to merge 1 commit into
Conversation
|
|
Hi @deepshekhardas, thanks for your interest in contributing! This project requires that pull request authors are vouched, and you are not in the list of vouched users. This PR will be closed automatically. See https://github.com/triggerdotdev/trigger.dev/blob/main/CONTRIBUTING.md for more details. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
WalkthroughThe webapp now accepts an optional ✨ 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 |
Rebased version of #3686. Adds RUNTIME_API_ORIGIN env var, which routes managed runner TRIGGER_API_URL/TRIGGER_STREAM_URL through an in-cluster origin (bypassing tracing gateways that rewrite traceparent). Dev CLI runs unaffected. Updates docker-compose, helm chart, .env.example, and docs. Closes #3686.