Evolutionary-Algorithms-On-Click / Evolutionary-Algorithms-On-Click/runner_controller_microservice
Make the rabbit MQ queue name dynamic.
- Dominant language
- Go
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/Evolutionary-Algorithms-On-Click/runner_controller_microservice/blob/6e10ff11c80ffa44c2b0f412a13aecaedd866094/util/enqueue.go#L45
Its hardcoded now. Instead take it from `env`. This will allow us to dynamically schedule tasks to different runners if more than one exist.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at util/enqueue.go around line 45 and inspect how environment values are read before the RabbitMQ queue is selected. Verify the queue name comes from env rather than a hardcoded value, then check the existing project tests or local service setup to confirm tasks can target different runners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, rabbitmq
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100