Open-EO / Open-EO/openeo-python-client
simplify job manager: `add_backend` without name
Open
Nobody has claimed this yet.
collect feedback
feature request
good first issue
job manager
low hanging fruit
nice-to-have
usability
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
To add a backend to MultiBackendJobManager, one has to give it a name, e.g.
job_manager.add_backend("foo", connection)
But that name has very little purpose. Can't we drop the requirement to provide a name, and just fall back on the connection url?
Contributor guide
No contributing guide indexed for this repository
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 MultiBackendJobManager and its add_backend method, then inspect the existing tests for backend registration. The change is complete when add_backend can be called without a name and uses the connection URL as the fallback identifier, with existing named calls still behaving correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100