-
Notifications
You must be signed in to change notification settings - Fork 42
Implement support for the Federation Extension #668
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
Comments
- for user API that's simpler to navigate - revert to methods iso properties (to allow future tweaks, e.g. return parsed object instead of raw dicts)
- for user API that's simpler to navigate - revert to methods iso properties (to allow future tweaks, e.g. return parsed object instead of raw dicts)
- for user API that's simpler to navigate - revert to methods iso properties (to allow future tweaks, e.g. return parsed object instead of raw dicts)
- for user API that's simpler to navigate - revert to methods iso properties (to allow future tweaks, e.g. return parsed object instead of raw dicts)
merged #716 with first bunch of additions to support federation extension |
Some initial docs are at https://open-eo.github.io/openeo-python-client/federation-extension.html |
but keep a bit of backward compatibility for now related to Open-EO/openeo-python-client#668
but keep a bit of backward compatibility for now related to Open-EO/openeo-python-client#668
planned to cover in current sprint:
|
most important parts of "programatic access in Python" are now covered I think. |
Most of the remaining TODOs are jupyter-integration related (Javascript/Vue). We don't have the expertise in the openEO team to work on these. |
I'll try to cover some of these as part of the next EOEPCA quarter. |
but keep a bit of backward compatibility for now related to Open-EO/openeo-python-client#668
I've implemented all open Jupyter-related tasks through #771, so handing back to VITO :-) |
Uh oh!
There was an error while loading. Please reload this page.
In the EOEPCA+ project, we made an evaluation of the federation-related functionality available through the openEO Python Client.
The Federation Extension can be found here: https://github.com/Open-EO/openeo-api/blob/draft/extensions/federation/README.md
The following issues have been identified for the programatic access in Python:
GET /
- Show federation backends (federation) -> possible but undocumented RESTCapabilities undocumented #610federation:missing
can't be accessed through the corresponding functions for the following endpoints:GET /collections
GET /processes
GET /process_graphs
GET /files
GET /jobs
GET /jobs/:id/logs
GET /services
GET /services/:id/logs
federation:backends
can't be accessed through the corresponding functions for the following endpoints:POST /validation
The following issues have been identified for the programatic access through the UI interface in notebooks such as Jupyter:
federation:missing
can't be accessed through the corresponding functions for the following endpoints:GET /collections
GET /processes
GET /file_formats
GET /process_graphs
GET /files
GET /jobs
GET /jobs/:id/logs
GET /services
GET /services/:id/logs
federation:backends
can't be accessed through the corresponding functions for the following endpoints:(=> has no UI component in the Python client, will warn in Python)POST /validation
GET /udf_runtimes
per versionGET /services/{id}
Related issue for the upstream issues in Vue Components: Open-EO/openeo-vue-components#97
The text was updated successfully, but these errors were encountered: