AutoMD
AutoMD is a documentation library for Flask APIs build with FlaskRESTful and Webargs. Endpoint parameters and basic responses are automatically parsed into the OpenAPI specification, using Type Hints and introspection, and a endpoints registered to serve the specification.
Motivation
Documentation libraries tend to rely heavily on elaborate docstrings and static generation from source code. This library requires minimal changes to existing code, and most information (especially parameter specs) doesn't rely on keeping docstrings up to date.
Installation
AutoMD is available through PyPi. AutoMD requires Python >= 3.6 (f-strings are too convenient to ignore) Install using pip:
pip install automd
AutoMD also install the following dependencies:
- flask
- flask-restful
- webargs
- apispec
- pyyaml
- marshmallow
- werkzeug
Usage
AutoMD registration/initialization
The first step is to initialize the AutoMD app from a FlaskRESTful Api.
from flask import Flask
from flask_restful import Api
from automd.registration import AutoMDApp
app: Flask = Flask(__name__)
api: Api = Api(app)
spec: AutoMDApp = AutoMDApp(api, title="AutoMD Test App", app_version="1.0.0", openapi_version="3.0.0")
After that, all that is required is adding the @automd decorator to an existing Resource endpoint.
from flask_restful import Resource
from marshmallow import fields
from webargs.flaskparser import use_kwargs
from automd.decorators import automd
class MinimalStatus(Resource):
get_query_arguments = {
"text": fields.String(required=False)
}
@automd()
@use_kwargs(get_query_arguments)
def get(self, text):
return text
which will mark the endpoint for inclusion in the OpenAPI spec. In this example, the spec information will be pretty limited, but will still have the API url, argument, and a default value.
With more complete python annotations, more information can be gleaned:
from flask_restful import Resource
from marshmallow import fields
from webargs.flaskparser import use_kwargs
from automd.decorators import automd
class IntrospectionStatus(Resource):
post_query_arguments = {
"text": fields.String(required=False)
}
@automd()
@use_kwargs(post_query_arguments, location="json")
def post(self, text: str = "Hello AutoMD") -> str:
ret_text: str = "status check OK"
if text is not None:
ret_text = f"{ret_text}: {text}"
return ret_text
From this the APISpec also get the parameter type, default value, and API response type. It does not get the parameter location yet though, that takes more aguements to automd.
Filling in more information in the webargs fields, automd decorator, use_kwargs decorator, and using one of the AutoMD response classes for type annotation and gives even better information:
from flask_restful import Resource
from marshmallow import fields
from webargs.flaskparser import use_kwargs
from automd.decorators import automd
from automd.responses import ValueResponse
class Status(Resource):
get_query_arguments = {
"text": fields.String(required=False, description='Text to return', doc_default="Hello AutoMD")
}
@automd(parameter_schema=get_query_arguments,
summary="Status Endpoint",
description="Status Endpoint, responds with a message made from the input string")
@use_kwargs(get_query_arguments, location="query")
def get(self, text: str = None) -> ValueResponse:
log_text: str = "status check OK"
log_text = f"{log_text}: {text or 'Hello AutoMD'}"
return ValueResponse(log_text)
With this information, argument types, return types, summaries, descriptions, detailed default information, and parameter location info (body, query, etc) is included. Summary and description are the only "magic strings" needed, and those will generally not change much or be onerous to keep up to date compared to the automatically grabbed information.
An example Flask API app is provided to showcase some functionality. Start it using run.py.
A sample of the OpenAPI spec generated is here.
Metadata
Release files for AutoMD 1.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| AutoMD-1.5.0.tar.gz | 11.6 kB | Without provenance | Details for AutoMD-1.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| AutoMD-1.5.0-py3-none-any.whl | Python 3 | none | any | Details for AutoMD-1.5.0-py3-none-any.whl |
Total release size: 26.4 kB
Release files / AutoMD-1.5.0.tar.gz
| Download URL | AutoMD-1.5.0.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd92ebaf0969f7ed819a88a4120ad7aaa234b733f14c8247549ad1aa5c91ff0c
|
|
BLAKE2b-256 checksum How to use checksums |
81bf6577b7598f40fc4ab221f03cb1b85879b724a262069d2b829fc9b2290858
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.2
|
Release files / AutoMD-1.5.0-py3-none-any.whl
| Download URL | AutoMD-1.5.0-py3-none-any.whl |
|---|---|
| Size | 14.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
001eb94b08b814031f19e12000877df6bfa007d19b8e77a1841fc2cbaaecf66c
|
|
BLAKE2b-256 checksum How to use checksums |
120ac9e77f7a262a2df3d9a7f07a0998eaf7fa4328876a10876fc32fe7597d46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.2
|
Security for AutoMD 1.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.