feat: automate local BenID pool top-up (no more manual Generate BenID… - #186
feat: automate local BenID pool top-up (no more manual Generate BenID…#186vishwab1 wants to merge 1 commit into
Conversation
… click) Adds BenIDPoolTopUpScheduler: on startup, bootstraps 10,000 BenIDs if the local pool is empty; daily at 6 PM, tops up by 1,000 if the pool has dropped below 5,000; retries hourly if a top-up attempt fails (no signal, timeout, or a garbled response are all treated as failure and retried, never as a partial success). Only runs on van/laptop deployments - reuses the existing stoptb.enforce.vanid / stoptb.van.id properties (already used by Identity-API/FLW-API/TM-API on the same laptop) as the guard, so this never fires on a central-deployed instance of MMU-API. An in-progress flag prevents two top-up attempts running at once. New config: benCheckUrlLocal, benid.pool.lowerLimit/batchSize/bootstrapSize, benGenSchedulerCredential (static server-to-server credential, since a scheduled job has no logged-in user session). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
|
1 participant
… click)
Adds BenIDPoolTopUpScheduler: on startup, bootstraps 10,000 BenIDs if the local pool is empty; daily at 6 PM, tops up by 1,000 if the pool has dropped below 5,000; retries hourly if a top-up attempt fails (no signal, timeout, or a garbled response are all treated as failure and retried, never as a partial success).
Only runs on van/laptop deployments - reuses the existing stoptb.enforce.vanid / stoptb.van.id properties (already used by Identity-API/FLW-API/TM-API on the same laptop) as the guard, so this never fires on a central-deployed instance of MMU-API. An in-progress flag prevents two top-up attempts running at once.
New config: benCheckUrlLocal, benid.pool.lowerLimit/batchSize/bootstrapSize, benGenSchedulerCredential (static server-to-server credential, since a scheduled job has no logged-in user session).
📋 Description
JIRA ID:
Please provide a summary of the change and the motivation behind it. Include relevant context and details.
✅ Type of Change
ℹ️ Additional Information
Please describe how the changes were tested, and include any relevant screenshots, logs, or other information that provides additional context.