daily cron job to send all the usernames from ashoat's keyserver to the identity service.
the logic here is very similar to the logic added to the account-creator.js
Depends on D8330
Details
Details
Modified cron job schedule to force a run and observed that usernames were added to the identity service's reserved usernames table locally
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
Instead of syncing it using chron, can't we call the API as a part of user registration / account deletion?
Comment Actions
We do that as well in D8300. This change is just for initial syncing and then in case of a network failure or identity service issue
| keyserver/src/cron/add-reserved-usernames.js | ||
|---|---|---|
| 11 ↗ | (On Diff #28174) | Let's name it more precisely |
| keyserver/src/cron/cron.js | ||
| 96 ↗ | (On Diff #28174) | It seems like we'll need to make sure this only runs on my keyserver. Can you create a follow-up Linear task before landing for this? If you don't already have a parent task for follow-ups, you can create one and add the new task as a child |
| 103 ↗ | (On Diff #28174) | |
| keyserver/src/cron/cron.js | ||
|---|---|---|
| 96 ↗ | (On Diff #28174) | |