[Bug]: Custom remote cache builds cannot be triggered on Vercel

[AdiRishi]

There have been bug reports that this project cannot be used when using Vercel builds for CI.

Reported here - #537 (comment)

I meant to enable the remote cache on Vercel builds.
Followed your instructions but vercel seems to inject their own teamId overwriting the specified env TURBO_TEAM, disabling access to the cloudflare cache

[shunkakinoki]

Thank you so much for the issue @AdiRishi

Please let me know how can I help 🙇‍♂️

[shunkakinoki]

@AdiRishi Any updates on your side? Would love to help make this work 🙏

[AdiRishi]

Hey @shunkakinoki I spent a bunch of time trying to experiement with this on Vercel. Basically what's happening is that Vercel will override the TURBO_TOKEN environment variable.
In my testing, it was making requests to the Cloudflare server, but they are all rejected as the value of TURBO_TOKEN is wrong.

Since that token it injects is a JWT, I doubt you'd be able to save it raw and use it as well.
I've asked about this on the Vercel community forum, lets see what they say - https://vercel.community/t/how-to-stop-vercel-from-injecting-and-overriding-the-turbo-token-env-var/1401

[AdiRishi]

@shunkakinoki Vercel has completed their fix for this and I've confirmed it works.
Here's how I had my environment variabels setup when testing on Vercel

Closing this issue now. Feel free to re-open if it doesn't work for you.

[shunkakinoki]

@AdiRishi Thank you so much for your tireless work - appreciate digging into this 🙏