-
Notifications
You must be signed in to change notification settings - Fork 4
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
ADR 6: REST API #31
ADR 6: REST API #31
Conversation
Just to make this more concrete. I would also propose the following stack to implement the API service.
|
|
||
We could also expose the datasets via the API. | ||
This of course overlaps with STAC stuff / catalogging stuff. | ||
It would be really cool to be able to track `dataset` ➡️ `recipe_run` ➡️ `feedstock` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More that really cool - I'd say imperative!
I also just read about fastapi-stac. So in theory we could eventually include a STAC component in a more general fastapi service. |
Adding a note here about the DataOne API, which is an interesting point of reference: https://releases.dataone.org/online/api-documentation-v2.0.1/apis/index.html |
closing as stale |
I am proposing we create a simple REST API to provide a central source of truth for Pangeo Forge Federation. Details in the PR.
comments welcome from @pangeo-forge/dev-team