-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openEO client config file #264
Comments
Interesting idea. This could get a bit complicated once it's not just Linux (e.g. user workspace mess on Windows). The JS client would only be able to read such files in Node and in Node there's no OIDC auth available as of now, but I haven't seen anyone use the JS client in a Node environment. So pretty low priority there, but I could see this as being an interesting option for R, indeed. Will open a respective issue there, too. |
Another config idea (inspired by https://github.com/openEOPlatform/architecture-docs/issues/116):
|
ConfigParser format load from env var, $CWD or home dir lazy loaded
ConfigParser format load from env var, $CWD or home dir lazy loaded
merge of #289 introduces basic config system |
another use case in this realm: |
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.
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.
The text was updated successfully, but these errors were encountered: