Disable the legacy GIVeconomy power sync cron#2315
Conversation
Default the impact-graph pull job to off so the old backend stops mirroring power changes once GIVeconomy becomes the source of truth. Made-with: Cursor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughAdded an environment variable-based early-exit gate to the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~7 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Issue
Summary
Stop the legacy impact-graph service from continuing to poll GIVeconomy for power updates once the new service becomes the source of truth. This makes the power cutover one-directional and keeps the old backend from reintroducing mirrored state after deployment.
Changes
DISABLE_GIVECONOMY_POWER_SYNC_JOB=falseis set explicitlyHow to Test
npx eslint "src/services/cronJobs/syncGiveconomyPowerEvents.ts".DISABLE_GIVECONOMY_POWER_SYNC_JOB=falseand confirm the cron can still be re-enabled intentionally.Made with Cursor
Summary by CodeRabbit