Open-EO / Open-EO/openeo-python-driver
Dynamic "config" system
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
Current config approaches in openeo-driver (and related) are static (e.g. env var based, or file based), and have to be updated with a full deploy pipeline (CI, deploy, promote, etc), which is perfectly fine for most things.
The client-credentials-to-user mapping is currently also a config item, but it is tedious that updates have to go through the deploy pipeline. This should better be moved to a more dynamic config system that can be updated on the fly (e.g. backed by Zookeeper or another DB). #245 would probably fit in this as well.
Some prior/related work of putting dynamic configs in zookeeper: eu-cdse/openeo-cdse-infra#33, Open-EO/openeo-geopyspark-driver#600
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 reviewing the current static client-credentials-to-user mapping and the related work in #245, then compare the prior ZooKeeper work in eu-cdse/openeo-cdse-infra#33 and Open-EO/openeo-geopyspark-driver#600. The work is done when configuration can be updated on the fly without the full deploy pipeline, with the storage approach and scope agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100