template-python-flask-api

Remaining TODO work

• encounter Service
• MongoIO
• server.py
• All Test Files

Now you can remove these instructions from the readme,

Overview

This is a simple Flask API that provides Get/Post/Patch services for documents in the Encounter collection. This API uses data from a backing Mongo Database, and supports a Single Page Application.

The OpenAPI specifications for the api can be found in the docs folder, and are served here

Prerequisites

• Mentorhub Developer Edition
• Python
• Pipenv

Optional

• Mongo Compass - if you want a way to look into the database

Install Dependencies

pipenv install

Run Unit Testing

pipenv run test

{re}start the containerized database and run the API locally

pipenv run local

Run the API locally (assumes database is already running)

pipenv run start

Build and run the API Container

pipenv run container

This will build the new container, and {re}start the mongodb and API container.

Run StepCI end-2-end testing

NOTE: Assumes the API is running at localhost:8088

pipenv run stepci

Run Load Tests

pipenv run load

Generates loads of test data

Project Layout

• /src this folder contains all source code
• /src/server.py is the main entrypoint, which initializes the configuration and registers routes with Flask
• /src/config/config.py is the singleton config object that manages configuration values and acts as a cache for enumerators and other low volatility data values.
• /src/models contains helpers related to creating transactional data objects such as breadcrumbs or RBAC tokens
• /src/routes contains Flask http request/response handlers
• /src/services service interface that wraps database calls with RBAC, encode/decode, and other business logic
• /src/utils/mongo_io.py is a singleton that manages the mongodb connection, and provides database io functions to the service layer.
• /test this folder contains unit testing, and testing artifacts. The sub-folder structure mimics the /src folder

API Testing with CURL

If you want to do more manual testing, here are the curl commands to use

Test Health Endpoint

This endpoint supports the prometheus monitoring standards for a healthcheck endpoint

curl http://localhost:8088/api/health/

Test Config Endpoint

curl http://localhost:8088/api/config/

Test get a Encounter document

curl http://localhost:8088/api/encounter/eeee00000000000000000001/

Test add a Encounter Document

curl -X POST localhost:8088/api/encounter/ \
-H "Content-Type: application/json" \
-d '{"date":"2024-12-07 00:00:00","mentorId":"aaaa00000000000000000005","personId":"aaaa00000000000000000024","planId":"eeff00000000000000000004","status":"Active"}'

Test update a Encounter Document

curl -X PATCH localhost:8088/api/encounter/eeee00000000000000000001 \
-H "Content-Type: application/json" \
-d '{"status":"Archived"}'

Test get a Plan document

curl http://localhost:8088/api/plan/eeff00000000000000000002/

Test add a Plan Document

curl -X POST localhost:8088/api/plan/ \
-H "Content-Type: application/json" \
-d '{"name":"test"}'

Test update a Plan Document

curl -X PATCH localhost:8088/api/plan/eeff00000000000000000002 \
-H "Content-Type: application/json" \
-d '{"status":"Archived"}'

Test get a list of People

curl http://localhost:8088/api/people/

Test get a list of Mentors

curl http://localhost:8088/api/mentors/

Observability and Configuration

The api/config/ endpoint will return a list of configuration values. These values are either "defaults" or loaded from an Environment Variable, or found in a singleton configuration file of the same name. Configuration files take precedence over environment variables. The variable "CONFIG_FOLDER" will change the location of configuration files from the default of ./

The api/health/ endpoint is a Prometheus Healthcheck endpoint.

The Dockerfile uses a 2-stage build, and sup8090s both amd64 and arm64 architectures.