fix(api-service): use NOVU_INTERNAL_SECRET_KEY for agents early access trigger#10688
fix(api-service): use NOVU_INTERNAL_SECRET_KEY for agents early access trigger#10688
Conversation
Co-authored-by: Dima Grossman <dima@grossman.io>
✅ Deploy Preview for dashboard-v2-novu-staging canceled.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
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 |
|
Hey there and thank you for opening this pull request! 👋 We require pull request titles to follow specific formatting rules and it looks like your proposed title needs to be adjusted. Your PR title is: Requirements:
Expected format: Details: PR title must end with 'fixes TICKET-ID' (e.g., 'fixes NOV-123') or include ticket ID in branch name |
The
POST /support/agents-early-accesshandler now readsNOVU_INTERNAL_SECRET_KEYinstead ofNOVU_SECRET_KEY, matching other server-side Novu triggers in the same controller (e.g.mobile-setup) and the internal secret already validated inenv.validators.ts.Breaking change: Deployments must set
NOVU_INTERNAL_SECRET_KEYfor this workflow to run; relying onNOVU_SECRET_KEYalone will no longer trigger the internal email.Slack Thread