Skip to content
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

/service_types: skip backend when its capabilities states it does not support /service_types #85

Closed
JohanKJSchreurs opened this issue Dec 7, 2022 · 4 comments

Comments

@JohanKJSchreurs
Copy link
Contributor

JohanKJSchreurs commented Dec 7, 2022

EODC backend (e.g.) does not support /service_types and we can know that beforehand (because it's not in capabilities doc), so we should skip it, instead of trying and needlessly logging a 404 error.

This is a follow up ticket for the to do's of #78, to plan and track the tasks separately .
See also: #78 (comment)

@soxofaan
Copy link
Member

soxofaan commented Dec 7, 2022

FYI: VITO back-end also stopped supporting /service_types since Open-EO/openeo-geopyspark-driver@c61b822 (I'm not sure if this change is in production already)

@soxofaan
Copy link
Member

soxofaan commented Dec 7, 2022

some info:

Start from a MultiBackendConnection and iterate through the upstream backends (BackendConnection objects), each of these has a capabilities() method, which returns an RESTCapabilities object. From that you should be able to check with supports_endpoint if /service_types is supported

@soxofaan
Copy link
Member

soxofaan commented Dec 7, 2022

another thing: I think it makes sense to store the result of this check in the housekeeping structure mentioned in #84 in some way

JohanKJSchreurs added a commit that referenced this issue Dec 13, 2022
soxofaan added a commit that referenced this issue Jan 18, 2023
@soxofaan
Copy link
Member

#87 was merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants