foca
foca copied to clipboard
elixir-cloud-aai
Opinionated Flask microservice archetype for quick OpenAPI-based microservice development
## Description A number of mypy errors were coming in since foca was not included as part of the flask config but was being consumed using the current app context...
# Description `config` doesn't seem to have `foca` as an attribute. Came across this while going through [this](https://github.com/elixir-cloud-aai/proWES/blob/25f0e593c956fcd450f0f112c06c62ac768c77fe/pro_wes/app.py#L32) code snippet.
## Problem To ensure that FOCA will be able to benefit from security and feature updates of the archetype's core dependencies, sooner or later it will be necessary to upgrade...
- [ ] Add support for py3.12 - [ ] Remove support for py3.8 (end of life: [2024-10](https://devguide.python.org/versions/)) - [ ] Use Python images built based on Debian Bookworm (v12)...
Currently, for the sake of completing the pipeline, we have ignored certain `mypy` errors. We need to work on a solution in order to make our code implementation compatible with...
Provide a config option that allows users to check their own permissions. In that case, the GET endpoints should be available to the users for any permissions that affect them.
Pagination is required while excessing permission rule data objects.
Reference: https://github.com/elixir-cloud-aai/foca/pull/109/files#r768258555 Case: In case the user utilizes the same database name/ collection name, `FOCA` needs to handle it robustly.
Access control uses the default function `generate_id` for creating identifiers for new objects. We need to support configurable parameters for the same. Currently, we are using the default support that...
This issue is blocked by #146. Once the client is implemented, we need to use that client in the `petstore` example to automatically set the permissions of a newly created...
Metadata
Owner
Metadata
Opinionated Flask microservice archetype for quick OpenAPI-based microservice development