Filer work to support pub/sub for Consumer status
Open
Entities Team
techdebt
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
As per the parent/epic tickets, the current mechanism of the Filer making an API call to Namex to change a NR to consumed needs to be changed over to publishing a message to a GCP queue.
Namex work is required for this (see #28726) and should be done first.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the Filer code that currently calls Namex to change an NR to consumed, then review the parent or epic tickets and prerequisite issue #28726. Confirm the GCP queue and message contract with the Namex work; done means the Filer publishes the status change instead of making the API call.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100