eodcgmbh / openeo-fastapi Goto Github PK

Add a middle ware to the api for exception handling. This just enables blanket consistency with how the API will return errors to the clients, instead of every exception having to be handled and conformant with the clients everywhere ( as that is an easy thing to get wrong once ).

Add basic Auth to API App.

** Low priorty & not required by anyone

Add project to pypi so that installation is possible.

Add DB model for shared tables and cols

Draft a basic framework for what was discussed at the previous meeting.

The framework needs to be able to:

1. Return an initialized fastapi application.
2. Take in a configurable client object, which will be submoduled in this package.

It would be good to demo this first iteration of the framework by implementing a few basic endpoints, and being able to override/ switch one of those endpoints off.

The simplest first endpoints to add would be,

capabilities -> "/"
well known -> "/.well-known/openeo"
conformance -> "/conformance"

Add logic to register a processes endpoint in the app.

Add openeo-processes-dask specs to core client.

Reference: https://github.com/stac-utils/stac-fastapi

Add locic to register Collections endpoint to app.

Add stac based base logic to core client.

https://github.com/stac-utils/stac-fastapi

Add Client based on SQL Alchemy to communicate with DB.

Add files Endpoint to app (and add it to CoreClient)

Add CoreClient to repo to a working App with core functionalits (processes, collections, file_formats ,...) shipped with the repo that can be overwritten by other clients.

Add

/health
/me
/validation
/udf_runtimes
/result