Open-EO / Open-EO/openeo-python-client
openEO client config file
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
openeo python client already supports using a config file for authentication related settings, but there is more opportunity for config file based configuration. E.g.
- https://github.com/Open-EO/openeo-python-client/issues/187
- https://github.com/Open-EO/openeo-python-client/issues/260
- default timeouts, retry settings, ...
- temp folders (e.g. for partial downloads)
- ...
While the auth config file is very user specific, these general configs are not privacy/security sensitive.
So we could support a layered approach with a system wide config (e.g. /etc/openeo.conf), a user specific config (e.g. /home/john/.openeo.conf), a project specific config (e.g. path/to/myproject/openeo.conf), env variables, ...
If possible, we could even have a common config approach with the R and JS client.
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 Python client's existing authentication config support and the related issues #187 and #260. Define the scope and precedence for system, user, project, and environment configuration, including timeouts, retries, and temporary folders; done requires an agreed design for any shared approach with the R and JavaScript clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100