Vecel preview with automation bypass not working
I'm trying to link my development environment of Novu to my vercel preview branch (our dev environment) and want to use vercel's automation bypass in the url in the Novu dashboard, but it's saying that it's not valid. I've confirmed that in incognito mode the bypass works and the novu enpoint can get hit, so I'm not sure what's going on here. My url looks like:
https://....url.../api/novu?x-vercel-protection-bypass=BYPASS_KEY
https://vercel.com/docs/security/deployment-protection/methods-to-bypass-deployment-protection/protection-bypass-automation
Environment ID: 66fc55c608355d6d570daac5
Protection Bypass for Automation
Learn how to bypass Vercel Deployment Protection for automated tooling (e.g. E2E testing).
5 Replies
It looks like the novu backend is adding query parameters for actions, the system probably needs to be able to handle arbitrary query parameters as part of the base URL as well? https://github.com/novuhq/novu/blob/next/apps/api/src/app/bridge/usecases/get-bridge-status/get-bridge-status.usecase.ts#L9
Another option could be the option to add custom headers into the bridge configuration for api keys that are needed to access the bridge url?
GitHub
feat: Added the ability to have query parameters in bridge checks b...
What changed? Why was the change needed?
We added the ability to have query parameters within the bridge urls. This is a requirement for any hosting service for the bridge where there are required ...
@elmd
Thanks for adding PR for this. Our team will take a look on this
Thanks! It’s currently blocking us from going live in our development environment
@Pawan Jain
@elmd DMed you