global orchestrator list
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
New database table: `region`
Example content:
```
{region: "otp", orchestrators: [{"address": "https://otp-orch-1.example.com:443"}]}
```
Two new endpoints:
### `PUT /api/region/:REGION`
* Requires admin token
* Creates or updates list of orchestrators for that region. Example body:
```
PUT /api/region/otp
{
region: "otp", orchestrators: [
{"address": "https://otp-orch-1.example.com:443"},
{"address": "https://otp-orch-2.example.com:443"}
]
}
```
### `GET /api/region/orchestrator`
* Returns a flat list of orchestrators suitable for consumption by go-livepeer's `-orchWebhookUrl` Example response:
```
[
{"address": "https://otp-orch-1.example.com:443"},
{"address": "https://otp-orch-2.example.com:443"},
{"address": "https://ewr-orch-1.example.com:443"},
{"address": "https://rkv-orch-1.example.com:443"}
]
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing database and API entry points that would handle the new `region` table and the `PUT /api/region/:REGION` and `GET /api/region/orchestrator` endpoints. Done means admin-authenticated updates create or replace regional orchestrator lists, while the GET endpoint returns one flat list suitable for go-livepeer's `-orchWebhookUrl`.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100