Pay queue for lear events
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Implement the alt-queue over a series of steps:
- [x] step1 - add minimal _publish_ to sbc-pay
- [ ] step2 - add filtering to send events to the correct subject (eg. business payments to business-queues)
- [ ] step3 - add on/off to the sbc-pay publishing per event type (FFlags or some other mapping to deploy)
- [ ] step4 - after sbc-pay moves to a newer python, replace this with the sbc-queue library (also use this to add features to the library)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing minimal _publish_ implementation in sbc-pay and the event types it handles. Trace how events are currently sent, then define the affected subjects and deployment controls needed for the remaining steps; done means filtering, per-event enablement, and the planned sbc-queue replacement are addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100