You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#426 established rigor for the existing FBC web interface which provided the entire catalog FBC to a client, and #451 intends to expand that web API to make the network traffic more efficient by providing the capability of limited-scope FBC query/response exchanges.
#426 established rigor for the existing FBC web interface which provided the entire catalog FBC to a client, and #451 intends to expand that web API to make the network traffic more efficient by providing the capability of limited-scope FBC query/response exchanges.
Catalogd exposes API endpoints in
status.urls
and currently only supports [base](https://github.com/operator-framework/catalogd/blob/main/docs/fetching-catalog-contents.md#fetching-clustercatalog-contents-from-the-catalogd-http-serverThis epic is to focus on API discovery).
We would like to permit some kind of api discovery, similar to https://api.openshift.com/ or https://docs.docker.com/reference/api/hub/latest/ where one can programmatically interrogate the OpenAPI spec for the interface and exercise a selected API.
The text was updated successfully, but these errors were encountered: