Firetail
===========
.. _FireTail's Documentation Page: https://firetail.readthedocs.org/en/latest/
.. _Connexion: https://github.com/spec-first/connexion
.. _Flask: https://flask.pocoo.org/
.. _issues waffle board: https://waffle.io/zalando/connexion
.. _API First: https://opensource.zalando.com/restful-api-guidelines/#api-first
.. _Hug: https://github.com/timothycrosley/hug
.. _Swagger: https://swagger.io/open-source-integrations/
.. _Jinja2: < https://jinja.pocoo.org/>
.. _rfc6750: https://tools.ietf.org/html/rfc6750
.. _OpenAPI Specification: https://www.openapis.org/
.. _OpenAPI 3.0 Style Values: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#style-values
.. _Operation Object: https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#operation-object
.. _swager.spec.security_definition: https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#security-definitions-object
.. _swager.spec.security_requirement: https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#security-requirement-object
.. _YAML format: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#format
.. _token information: https://tools.ietf.org/html/rfc6749
.. _Tornado: https://www.tornadoweb.org/en/stable/
.. _Connexion Pet Store Example Application: https://github.com/hjacobs/connexion-example
.. _described by Flask: https://flask.pocoo.org/snippets/111/
.. _werkzeug: https://werkzeug.pocoo.org/
.. _Connexion's Documentation Page: https://connexion.readthedocs.org/en/latest/
.. _Crafting effective Microservices in Python: https://jobs.zalando.com/tech/blog/crafting-effective-microservices-in-python/
.. _issues where we are looking for contributions: https://github.com/FireTail-io/firetail-py-lib/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22
.. _HTTP Methods work in Flask: https://flask.pocoo.org/docs/1.0/quickstart/#http-methods
.. .. image:: https://badges.gitter.im/zalando/connexion.svg
.. :alt: Join the chat at https://gitter.im/zalando/connexion
.. :target: https://gitter.im/zalando/connexion?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge
.. image:: https://github.com/FireTail-io/firetail-py-lib/actions/workflows/pipeline.yml/badge.svg
:alt: Build status
:target: https://github.com/FireTail-io/firetail-py-lib/actions/workflows/pipeline.yml
.. .. image:: https://coveralls.io/repos/github/zalando/connexion/badge.svg?branch=main
.. :target: https://coveralls.io/github/zalando/connexion?branch=main
.. :alt: Coveralls status
.. image:: https://img.shields.io/pypi/v/firetail.svg
:target: https://pypi.python.org/pypi/firetail
:alt: Latest Version
.. image:: https://img.shields.io/pypi/status/firetail.svg
:target: https://pypi.python.org/pypi/firetail
:alt: Development Status
.. image:: https://img.shields.io/pypi/pyversions/firetail.svg
:target: https://pypi.python.org/pypi/firetail
:alt: Python Versions
.. image:: https://img.shields.io/pypi/l/firetail.svg
:target: https://raw.githubusercontent.com/FireTail-io/firetail-py-lib/main/LICENSE.txt
:alt: License
FireTail is a framework that automagically handles HTTP requests by utilizing the OpenAPI Specification (formerly known as Swagger Spec) of your API described in YAML format.
Unlike many tools that generate specifications from Python code, FireTail enables you to write an OpenAPI specification, then FireTail handles the mapping of the endpoints to your Python functions.
You can describe your REST API in as much detail as you want; FireTail guarantees that it will work as you specified.
FireTail features:
--------------------
- Automated validation of requests and endpoint parameters based on your specification.
- A Web Swagger Console UI that allows users of your API to have
live documentation and even call your API's endpoints
through it.
- Handles OAuth 2 token-based authentication.
- Supports API versioning.
- Automatic payload serialization: If your specification defines that an endpoint
returns JSON, FireTail automatically serializes the return value and sets the
right content type in the HTTP header.
Why FireTail
--------------
With FireTail, you write the spec first. Subsequently, FireTail then calls your Python code, handling the mapping from the specification to the code. This approach encourages you to write the specification so that all of your developers can understand your API’s functionality, even before a single line of code is written.
If your APIs serve multiple teams, you can use Firetail to easily send them the documentation of your API, ensuring adherence to the specification you have written. This sets FireTail apart from frameworks like Hug_, which generates specifications *after* code has been written. Some disadvantages of generating specifications based on code is their tendency to lack detail or mix your documentation with the application's code logic.
.. Other Sources/Mentions
.. ----------------------
.. - Zalando RESTful API guidelines with `API First`_
.. - Blog post: `Crafting effective Microservices in Python`_
What's in FireTail 1.0:
------------------------
- App and API options must be provided through the "options" argument (``old_style_options`` have been removed).
- You must specify a form content-type in 'consumes' in order to consume form data.
- The `Operation` interface has been formalized in the `AbstractOperation` class.
- The `Operation` class has been renamed to `Swagger2Operation`.
- Array parameter deserialization now follows the Swagger 2.0 spec more closely.
In situations when a query parameter is passed multiple times, and the collectionFormat is either csv or pipes, the right-most value will be used.
For example, `?q=1,2,3&q=4,5,6` will result in `q = [4, 5, 6]`.
The old behavior is available by setting the collectionFormat to `multi`, or by importing `decorators.uri_parsing.AlwaysMultiURIParser` and passing `parser_class=AlwaysMultiURIParser` to your API.
- The spec validator library has changed from `swagger-spec-validator` to `openapi-spec-validator`.
- Errors that previously raised `SwaggerValidationError` now raise the `InvalidSpecification` exception.
All spec validation errors should be wrapped with `InvalidSpecification`.
- Support for nullable/x-nullable, readOnly and writeOnly/x-writeOnly has been added to the standard json schema validator.
- Custom validators can now be specified on an API level (instead of on an app level).
- Added support for basic authentication and apikey authentication
- If unsupported security requirements are defined or ``x-tokenInfoFunc``/``x-tokenInfoUrl`` is missing, FireTail now denies requests instead of allowing access without security-check.
- Accessing ``firetail.request.user`` / ``flask.request.user`` is no longer supported, use ``firetail.context['user']`` instead.
How to Use
==========
Prerequisites
-------------
Python 3.6+
Installing It
-------------
In your command line, type:
.. code-block:: bash
$ pip install firetail
Running It
----------
Place your API YAML inside a folder in the root
path of your application (e.g ``swagger/``). Then run:
.. code-block:: python
import firetail
app = firetail.App(__name__, specification_dir='swagger/')
app.add_api('my_api.yaml')
app.run(port=8080)
See the `Connexion Pet Store Example Application`_ for a sample
specification.
Now you're able to run and use FireTail!
OAuth 2 Authentication and Authorization
----------------------------------------
FireTail supports one of the three OAuth 2 handling methods. (See
"TODO" below.) With FireTail, the API security definition **must**
include a 'x-tokenInfoUrl' or 'x-tokenInfoFunc (or set ``TOKENINFO_URL``
or ``TOKENINFO_FUNC`` env var respectively). 'x-tokenInfoUrl' must contain an
URL to validate and get the `token information`_ and 'x-tokenInfoFunc must
contain a reference to a function used to obtain the token info. When both 'x-tokenInfoUrl'
and 'x-tokenInfoFunc' are used, FireTail will prioritize the function method. FireTail expects to
receive the OAuth token in the ``Authorization`` header field in the
format described in `rfc6750`_ section 2.1. This aspect
represents a significant difference from the usual OAuth flow.
Dynamic Rendering of Your Specification
---------------------------------------
FireTail uses Jinja2_ to allow specification parameterization through the ``arguments`` parameter. You can define specification arguments for the application either globally (via the ``firetail.App`` constructor) or for each specific API (via the firetail ion.App#add_api`` method):
.. code-block:: python
app = firetail.App(__name__, specification_dir='swagger/',
arguments={'global': 'global_value'})
app.add_api('my_api.yaml', arguments={'api_local': 'local_value'})
app.run(port=8080)
When a value is provided both globally and on the API, the API value will take precedence.
Endpoint Routing to Your Python Views
-------------------------------------
FireTail uses the ``operationId`` from each `Operation Object`_ to
identify which Python function should handle each URL.
**Explicit Routing**:
.. code-block:: yaml
paths:
/hello_world:
post:
operationId: myapp.api.hello_world
If you provide this path in your specification POST requests to
`` https://MYHOST/hello_world``, it will be handled by the function
``hello_world`` in the ``myapp.api`` module. Optionally, you can include
``x-swagger-router-controller`` (or ``x-openapi-router-controller``) in your
operation definition, making ``operationId`` relative:
.. code-block:: yaml
paths:
/hello_world:
post:
x-swagger-router-controller: myapp.api
operationId: hello_world
Keep in mind that FireTail follows how `HTTP methods work in Flask`_ and therefore HEAD requests will be handled by the ``operationId`` specified under GET in the specification. If both methods are supported, ``firetail.request.method`` can be used to determine which request was made.
Automatic Routing
-----------------
To customize this behavior, FireTail can use alternative
``Resolvers``--for example, ``RestyResolver``. The ``RestyResolver``
will compose an ``operationId`` based on the path and HTTP method of
the endpoints in your specification:
.. code-block:: python
from firetail.resolver import RestyResolver
app = firetail.App(__name__)
app.add_api('swagger.yaml', resolver=RestyResolver('api'))
.. code-block:: yaml
paths:
/:
get:
# Implied operationId: api.get
/foo:
get:
# Implied operationId: api.foo.search
post:
# Implied operationId: api.foo.post
'/foo/{id}':
get:
# Implied operationId: api.foo.get
put:
# Implied operationId: api.foo.put
copy:
# Implied operationId: api.foo.copy
delete:
# Implied operationId: api.foo.delete
``RestyResolver`` will give precedence to any ``operationId`` encountered in the specification. It will also respect
``x-router-controller``. You can import and extend ``firetail.resolver.Resolver`` to implement your own ``operationId``
(and function) resolution algorithm.
Automatic Parameter Handling
----------------------------
FireTail automatically maps the parameters defined in your endpoint specification to arguments of your Python views as named parameters, and, whenever possible, with value casting. Simply define the endpoint's parameters with the same names as your views arguments.
As an example, say you have an endpoint specified as:
.. code-block:: yaml
paths:
/foo:
get:
operationId: api.foo_get
parameters:
- name: message
description: Some message.
in: query
type: string
required: true
And the view function:
.. code-block:: python
# api.py file
def foo_get(message):
# do something
return 'You send the message: {}'.format(message), 200
In this example, FireTail automatically recognizes that your view
function expects an argument named ``message`` and assigns the value
of the endpoint parameter ``message`` to your view function.
.. note:: In the OpenAPI 3.x.x spec, the requestBody does not have a name.
By default it will be passed in as 'body'. You can optionally
provide the x-body-name parameter in your requestBody
(or legacy position within the requestBody schema)
to override the name of the parameter that will be passed to your
handler function.
.. code-block:: yaml
/path
post:
requestBody:
x-body-name: body
content:
application/json:
schema:
# legacy location here should be ignored because the preferred location for x-body-name is at the requestBody level above
x-body-name: this_should_be_ignored
$ref: '#/components/schemas/someComponent'
.. warning:: When you define a parameter at your endpoint as *not* required, and
this argument does not have default value in your Python view, you will get
a "missing positional argument" exception whenever you call this endpoint
WITHOUT the parameter. Provide a default value for a named argument or use
``**kwargs`` dict.
Type casting
^^^^^^^^^^^^
Whenever possible, Firetail will try to parse your argument values and
do type casting to related Python native values. The current
available type castings are:
+--------------+-------------+
| OpenAPI Type | Python Type |
+==============+=============+
| integer | int |
+--------------+-------------+
| string | str |
+--------------+-------------+
| number | float |
+--------------+-------------+
| boolean | bool |
+--------------+-------------+
| array | list |
+--------------+-------------+
| null | None |
+--------------+-------------+
| object | dict |
+--------------+-------------+
If you use the ``array`` type In the Swagger definition, you can define the
``collectionFormat`` so that it won't be recognized. FireTail currently
supports collection formats "pipes" and "csv". The default format is "csv".
FireTail is opinionated about how the URI is parsed for ``array`` types.
The default behavior for query parameters that have been defined multiple
times is to use the right-most value. For example, if you provide a URI with
the the query string ``?letters=a,b,c&letters=d,e,f``, FireTail will set
``letters = ['d', 'e', 'f']``.
You can override this behavior by specifying the URI parser in the app or
api options.
.. code-block:: python
from firetail.decorators.uri_parsing import AlwaysMultiURIParser
options = {'uri_parser_class': AlwaysMultiURIParser}
app = firetail.App(__name__, specification_dir='swagger/', options=options)
You can implement your own URI parsing behavior by inheriting from
``firetail.decorators.uri_parsing.AbstractURIParser``.
There are a handful of URI parsers included with connection.
+----------------------+---------------------------------------------------------------------------+
| OpenAPIURIParser | This parser adheres to the OpenAPI 3.x.x spec, and uses the ``style`` |
| default: OpenAPI 3.0 | parameter. Query parameters are parsed from left to right, so if a query |
| | parameter is defined twice, then the right-most definition will take |
| | precedence. For example, if you provided a URI with the query string |
| | ``?letters=a,b,c&letters=d,e,f``, and ``style: simple``, then FireTail |
| | will set ``letters = ['d', 'e', 'f']``. For additional information see |
| | `OpenAPI 3.0 Style Values`_. |
+----------------------+---------------------------------------------------------------------------+
| Swagger2URIParser | This parser adheres to the Swagger 2.0 spec, and will only join together |
| default: OpenAPI 2.0 | multiple instance of the same query parameter if the ``collectionFormat`` |
| | is set to ``multi``. Query parameters are parsed from left to right, so |
| | if a query parameter is defined twice, then the right-most definition |
| | wins. For example, if you provided a URI with the query string |
| | ``?letters=a,b,c&letters=d,e,f``, and ``collectionFormat: csv``, then |
| | FireTail will set ``letters = ['d', 'e', 'f']`` |
+----------------------+---------------------------------------------------------------------------+
| FirstValueURIParser | This parser behaves like the Swagger2URIParser, except that it prefers |
| | the first defined value. For example, if you provided a URI with the query|
| | string ``?letters=a,b,c&letters=d,e,f`` and ``collectionFormat: csv`` |
| | then FireTail will set ``letters = ['a', 'b', 'c']`` |
+----------------------+---------------------------------------------------------------------------+
| AlwaysMultiURIParser | This parser is backwards compatible with FireTail 1.x. It joins together |
| | multiple instances of the same query parameter. |
+----------------------+---------------------------------------------------------------------------+
Parameter validation
^^^^^^^^^^^^^^^^^^^^
FireTail can apply strict parameter validation for query and form data
parameters. When this is enabled, requests that include parameters not defined
in the swagger spec return a 400 error. You can enable it when adding the API
to your application:
.. code-block:: python
app.add_api('my_apy.yaml', strict_validation=True)
API Versioning and basePath
---------------------------
Setting a base path is useful for versioned APIs. An example of
a base path would be the ``1.0`` in `` https://MYHOST/1.0/hello_world``.
If you are using OpenAPI 3.x.x, you set your base URL path in the
servers block of the specification. You can either specify a full
URL, or just a relative path.
.. code-block:: yaml
servers:
- url: https://MYHOST/1.0
description: full url example
- url: /1.0
description: relative path example
paths:
...
If you are using OpenAPI 2.0, you can define a ``basePath`` on the top level
of your OpenAPI 2.0 specification.
.. code-block:: yaml
basePath: /1.0
paths:
...
If you don't want to include the base path in your specification, you
can provide it when adding the API to your application:
.. code-block:: python
app.add_api('my_api.yaml', base_path='/1.0')
Swagger JSON
------------
FireTail makes the OpenAPI/Swagger specification in JSON format
available from either ``swagger.json`` (for OpenAPI 2.0) or
``openapi.json`` (for OpenAPI 3.x.x) at the base path of the API.
For example, if your base path was ``1.0``, then your spec would be
available at ``/1.0/openapi.json``.
You can disable serving the spec JSON at the application level:
.. code-block:: python
options = {"serve_spec": False}
app = firetail.App(__name__, specification_dir='openapi/',
options=options)
app.add_api('my_api.yaml')
You can also disable it at the API level:
.. code-block:: python
options = {"serve_spec": False}
app = firetail.App(__name__, specification_dir='openapi/')
app.add_api('my_api.yaml', options=options)
HTTPS Support
-------------
When specifying HTTPS as the scheme in the API YAML file, all the URIs
in the served Swagger UI are HTTPS endpoints. The problem: The default
server that runs is a "normal" HTTP server. This means that the
Swagger UI cannot be used to play with the API. What is the correct
way to start a HTTPS server when using FireTail?
One way, `described by Flask`_, looks like this:
.. code-block:: python
from OpenSSL import SSL
context = SSL.Context(SSL.SSLv23_METHOD)
context.use_privatekey_file('yourserver.key')
context.use_certificate_file('yourserver.crt')
app.run(host='127.0.0.1', port='12344',
debug=False/True, ssl_context=context)
However, FireTail doesn't provide an ssl_context parameter. This is
because Flask doesn't, either--but it uses ``**kwargs`` to send the
parameters to the underlying `werkzeug`_ server.
The Swagger UI Console
----------------------
The Swagger UI for an API is available through pip extras.
You can install it with ``pip install firetail[swagger-ui]``.
It will be served up at ``{base_path}/ui/`` where ``base_path`` is the
base path of the API.
You can disable the Swagger UI at the application level:
.. code-block:: python
app = firetail.App(__name__, specification_dir='openapi/',
options={"swagger_ui": False})
app.add_api('my_api.yaml')
You can also disable it at the API level:
.. code-block:: python
app = firetail.App(__name__, specification_dir='openapi/')
app.add_api('my_api.yaml', options={"swagger_ui": False})
If necessary, you can explicitly specify the path to the directory with
swagger-ui to not use the firetail[swagger-ui] distro.
In order to do this, you should specify the following option:
.. code-block:: python
options = {'swagger_path': '/path/to/swagger_ui/'}
app = firetail.App(__name__, specification_dir='openapi/', options=options)
If you wish to provide your own swagger-ui distro, note that FireTail
expects a jinja2 file called ``swagger_ui/index.j2`` in order to load the
correct ``swagger.json`` by default. Your ``index.j2`` file can use the
``openapi_spec_url`` jinja variable for this purpose:
.. code-block::
const ui = SwaggerUIBundle({ url: "{{ openapi_spec_url }}"})
Additionally, if you wish to use swagger-ui-3.x.x, it is also provided by
installing firetail[swagger-ui], and can be enabled like this:
.. code-block:: python
from swagger_ui_bundle import swagger_ui_3_path
options = {'swagger_path': swagger_ui_3_path}
app = firetail.App(__name__, specification_dir='swagger/', options=options)
Server Backend
--------------
By default FireTail uses the Flask_ server. For asynchronous
applications, you can also use Tornado_ as the HTTP server. To do
this, set your server to ``tornado``:
.. code-block:: python
import firetail
app = firetail.App(__name__, specification_dir='swagger/')
app.run(server='tornado', port=8080)
You can use the Flask WSGI app with any WSGI container, e.g. `using
Flask with uWSGI`_ (this is common):
.. code-block:: python
app = firetail.App(__name__, specification_dir='swagger/')
application = app.app # expose global WSGI application object
Set up and run the installation code:
.. code-block:: bash
$ sudo pip3 install uwsgi
$ uwsgi --http :8080 -w app -p 16 # use 16 worker processes
See the `uWSGI documentation`_ for more information.
.. _using Flask with uWSGI: https://flask.pocoo.org/docs/latest/deploying/uwsgi/
.. _uWSGI documentation: https://uwsgi-docs.readthedocs.org/
Documentation
=============
Additional information is available at `FireTail's Documentation Page`_.
Changes
=======
A full changelog is maintained on the `GitHub releases page`_.
.. _GitHub releases page: https://github.com/FireTail-io/firetail-py-lib/releases
Contributing to FireTail/TODOs
================================
We welcome your ideas, issues, and pull requests. Just follow the
usual/standard GitHub practices.
Unless you explicitly state otherwise in advance, any non trivial
contribution intentionally submitted for inclusion in this project by you
to the steward of this repository (Point Security Inc DBA FireTail (TM)) shall be under the
terms and conditions of Lesser General Public License 2.0 written below, without any
additional copyright information, terms or conditions.
TODOs
-----
License
===================
Copyright 2022 Point Security Inc DBA FireTail (TM)
Licensed under the Lesser General Public License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.gnu.org/licenses/lgpl-3.0.txt.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Raw data
{
"_id": null,
"home_page": "https://github.com/FireTail-io/firetail-py-lib",
"name": "firetail",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.6",
"maintainer_email": null,
"keywords": "openapi oai swagger rest api oauth flask microservice framework",
"author": "FireTail International (TM)",
"author_email": null,
"download_url": "https://files.pythonhosted.org/packages/40/c4/15b97397f583e488cee99ea8e83f3d5fa9e07dc60870e71f458bdd48ab1c/firetail-1.1.0.tar.gz",
"platform": null,
"description": "Firetail \n===========\n.. _FireTail's Documentation Page: https://firetail.readthedocs.org/en/latest/\n.. _Connexion: https://github.com/spec-first/connexion\n.. _Flask: https://flask.pocoo.org/\n.. _issues waffle board: https://waffle.io/zalando/connexion\n.. _API First: https://opensource.zalando.com/restful-api-guidelines/#api-first\n.. _Hug: https://github.com/timothycrosley/hug\n.. _Swagger: https://swagger.io/open-source-integrations/\n.. _Jinja2: < https://jinja.pocoo.org/>\n.. _rfc6750: https://tools.ietf.org/html/rfc6750\n.. _OpenAPI Specification: https://www.openapis.org/\n.. _OpenAPI 3.0 Style Values: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#style-values\n.. _Operation Object: https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#operation-object\n.. _swager.spec.security_definition: https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#security-definitions-object\n.. _swager.spec.security_requirement: https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#security-requirement-object\n.. _YAML format: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#format\n.. _token information: https://tools.ietf.org/html/rfc6749\n.. _Tornado: https://www.tornadoweb.org/en/stable/\n.. _Connexion Pet Store Example Application: https://github.com/hjacobs/connexion-example\n.. _described by Flask: https://flask.pocoo.org/snippets/111/\n.. _werkzeug: https://werkzeug.pocoo.org/\n.. _Connexion's Documentation Page: https://connexion.readthedocs.org/en/latest/\n.. _Crafting effective Microservices in Python: https://jobs.zalando.com/tech/blog/crafting-effective-microservices-in-python/\n.. _issues where we are looking for contributions: https://github.com/FireTail-io/firetail-py-lib/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22\n.. _HTTP Methods work in Flask: https://flask.pocoo.org/docs/1.0/quickstart/#http-methods\n\n.. .. image:: https://badges.gitter.im/zalando/connexion.svg\n.. :alt: Join the chat at https://gitter.im/zalando/connexion\n.. :target: https://gitter.im/zalando/connexion?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge\n\n.. image:: https://github.com/FireTail-io/firetail-py-lib/actions/workflows/pipeline.yml/badge.svg\n :alt: Build status\n :target: https://github.com/FireTail-io/firetail-py-lib/actions/workflows/pipeline.yml\n\n.. .. image:: https://coveralls.io/repos/github/zalando/connexion/badge.svg?branch=main\n.. :target: https://coveralls.io/github/zalando/connexion?branch=main\n.. :alt: Coveralls status\n\n.. image:: https://img.shields.io/pypi/v/firetail.svg\n :target: https://pypi.python.org/pypi/firetail\n :alt: Latest Version\n\n.. image:: https://img.shields.io/pypi/status/firetail.svg\n :target: https://pypi.python.org/pypi/firetail\n :alt: Development Status\n\n.. image:: https://img.shields.io/pypi/pyversions/firetail.svg\n :target: https://pypi.python.org/pypi/firetail\n :alt: Python Versions\n\n.. image:: https://img.shields.io/pypi/l/firetail.svg\n :target: https://raw.githubusercontent.com/FireTail-io/firetail-py-lib/main/LICENSE.txt\n :alt: License\n\nFireTail is a framework that automagically handles HTTP requests by utilizing the OpenAPI Specification (formerly known as Swagger Spec) of your API described in YAML format. \nUnlike many tools that generate specifications from Python code, FireTail enables you to write an OpenAPI specification, then FireTail handles the mapping of the endpoints to your Python functions. \nYou can describe your REST API in as much detail as you want; FireTail guarantees that it will work as you specified.\n\nFireTail features:\n--------------------\n\n- Automated validation of requests and endpoint parameters based on your specification.\n- A Web Swagger Console UI that allows users of your API to have \n live documentation and even call your API's endpoints\n through it.\n- Handles OAuth 2 token-based authentication.\n- Supports API versioning.\n- Automatic payload serialization: If your specification defines that an endpoint\n returns JSON, FireTail automatically serializes the return value and sets the \n right content type in the HTTP header.\n\nWhy FireTail\n--------------\n\nWith FireTail, you write the spec first. Subsequently, FireTail then calls your Python code, handling the mapping from the specification to the code. This approach encourages you to write the specification so that all of your developers can understand your API\u2019s functionality, even before a single line of code is written.\n\nIf your APIs serve multiple teams, you can use Firetail to easily send them the documentation of your API, ensuring adherence to the specification you have written. This sets FireTail apart from frameworks like Hug_, which generates specifications *after* code has been written. Some disadvantages of generating specifications based on code is their tendency to lack detail or mix your documentation with the application's code logic.\n\n.. Other Sources/Mentions\n.. ----------------------\n\n.. - Zalando RESTful API guidelines with `API First`_\n.. - Blog post: `Crafting effective Microservices in Python`_\n\nWhat's in FireTail 1.0:\n------------------------\n- App and API options must be provided through the \"options\" argument (``old_style_options`` have been removed).\n- You must specify a form content-type in 'consumes' in order to consume form data.\n- The `Operation` interface has been formalized in the `AbstractOperation` class.\n- The `Operation` class has been renamed to `Swagger2Operation`.\n- Array parameter deserialization now follows the Swagger 2.0 spec more closely.\n In situations when a query parameter is passed multiple times, and the collectionFormat is either csv or pipes, the right-most value will be used.\n For example, `?q=1,2,3&q=4,5,6` will result in `q = [4, 5, 6]`.\n The old behavior is available by setting the collectionFormat to `multi`, or by importing `decorators.uri_parsing.AlwaysMultiURIParser` and passing `parser_class=AlwaysMultiURIParser` to your API.\n- The spec validator library has changed from `swagger-spec-validator` to `openapi-spec-validator`.\n- Errors that previously raised `SwaggerValidationError` now raise the `InvalidSpecification` exception.\n All spec validation errors should be wrapped with `InvalidSpecification`.\n- Support for nullable/x-nullable, readOnly and writeOnly/x-writeOnly has been added to the standard json schema validator.\n- Custom validators can now be specified on an API level (instead of on an app level).\n- Added support for basic authentication and apikey authentication\n- If unsupported security requirements are defined or ``x-tokenInfoFunc``/``x-tokenInfoUrl`` is missing, FireTail now denies requests instead of allowing access without security-check.\n- Accessing ``firetail.request.user`` / ``flask.request.user`` is no longer supported, use ``firetail.context['user']`` instead.\n\nHow to Use\n==========\n\nPrerequisites\n-------------\n\nPython 3.6+\n\nInstalling It\n-------------\n\nIn your command line, type:\n\n.. code-block:: bash\n\n $ pip install firetail\n\nRunning It\n----------\n\nPlace your API YAML inside a folder in the root\npath of your application (e.g ``swagger/``). Then run:\n\n.. code-block:: python\n\n import firetail\n\n app = firetail.App(__name__, specification_dir='swagger/')\n app.add_api('my_api.yaml')\n app.run(port=8080)\n\nSee the `Connexion Pet Store Example Application`_ for a sample\nspecification.\n\nNow you're able to run and use FireTail!\n\n\nOAuth 2 Authentication and Authorization\n----------------------------------------\n\nFireTail supports one of the three OAuth 2 handling methods. (See\n\"TODO\" below.) With FireTail, the API security definition **must**\ninclude a 'x-tokenInfoUrl' or 'x-tokenInfoFunc (or set ``TOKENINFO_URL``\nor ``TOKENINFO_FUNC`` env var respectively). 'x-tokenInfoUrl' must contain an\nURL to validate and get the `token information`_ and 'x-tokenInfoFunc must\ncontain a reference to a function used to obtain the token info. When both 'x-tokenInfoUrl'\nand 'x-tokenInfoFunc' are used, FireTail will prioritize the function method. FireTail expects to\nreceive the OAuth token in the ``Authorization`` header field in the\nformat described in `rfc6750`_ section 2.1. This aspect\nrepresents a significant difference from the usual OAuth flow.\n\nDynamic Rendering of Your Specification\n---------------------------------------\n\nFireTail uses Jinja2_ to allow specification parameterization through the ``arguments`` parameter. You can define specification arguments for the application either globally (via the ``firetail.App`` constructor) or for each specific API (via the firetail ion.App#add_api`` method):\n\n.. code-block:: python\n\n app = firetail.App(__name__, specification_dir='swagger/',\n arguments={'global': 'global_value'})\n app.add_api('my_api.yaml', arguments={'api_local': 'local_value'})\n app.run(port=8080)\n\nWhen a value is provided both globally and on the API, the API value will take precedence.\n\nEndpoint Routing to Your Python Views\n-------------------------------------\n\nFireTail uses the ``operationId`` from each `Operation Object`_ to\nidentify which Python function should handle each URL.\n\n**Explicit Routing**:\n\n.. code-block:: yaml\n\n paths:\n /hello_world:\n post:\n operationId: myapp.api.hello_world\n\nIf you provide this path in your specification POST requests to\n`` https://MYHOST/hello_world``, it will be handled by the function\n``hello_world`` in the ``myapp.api`` module. Optionally, you can include\n``x-swagger-router-controller`` (or ``x-openapi-router-controller``) in your\noperation definition, making ``operationId`` relative:\n\n.. code-block:: yaml\n\n paths:\n /hello_world:\n post:\n x-swagger-router-controller: myapp.api\n operationId: hello_world\n\nKeep in mind that FireTail follows how `HTTP methods work in Flask`_ and therefore HEAD requests will be handled by the ``operationId`` specified under GET in the specification. If both methods are supported, ``firetail.request.method`` can be used to determine which request was made.\n\nAutomatic Routing\n-----------------\n\nTo customize this behavior, FireTail can use alternative\n``Resolvers``--for example, ``RestyResolver``. The ``RestyResolver``\nwill compose an ``operationId`` based on the path and HTTP method of\nthe endpoints in your specification:\n\n.. code-block:: python\n\n from firetail.resolver import RestyResolver\n\n app = firetail.App(__name__)\n app.add_api('swagger.yaml', resolver=RestyResolver('api'))\n\n.. code-block:: yaml\n\n paths:\n /:\n get:\n # Implied operationId: api.get\n /foo:\n get:\n # Implied operationId: api.foo.search\n post:\n # Implied operationId: api.foo.post\n\n '/foo/{id}':\n get:\n # Implied operationId: api.foo.get\n put:\n # Implied operationId: api.foo.put\n copy:\n # Implied operationId: api.foo.copy\n delete:\n # Implied operationId: api.foo.delete\n\n``RestyResolver`` will give precedence to any ``operationId`` encountered in the specification. It will also respect\n``x-router-controller``. You can import and extend ``firetail.resolver.Resolver`` to implement your own ``operationId``\n(and function) resolution algorithm.\n\nAutomatic Parameter Handling\n----------------------------\n\nFireTail automatically maps the parameters defined in your endpoint specification to arguments of your Python views as named parameters, and, whenever possible, with value casting. Simply define the endpoint's parameters with the same names as your views arguments.\n\nAs an example, say you have an endpoint specified as:\n\n.. code-block:: yaml\n\n paths:\n /foo:\n get:\n operationId: api.foo_get\n parameters:\n - name: message\n description: Some message.\n in: query\n type: string\n required: true\n\nAnd the view function:\n\n.. code-block:: python\n\n # api.py file\n\n def foo_get(message):\n # do something\n return 'You send the message: {}'.format(message), 200\n\nIn this example, FireTail automatically recognizes that your view\nfunction expects an argument named ``message`` and assigns the value\nof the endpoint parameter ``message`` to your view function.\n\n.. note:: In the OpenAPI 3.x.x spec, the requestBody does not have a name.\n By default it will be passed in as 'body'. You can optionally\n provide the x-body-name parameter in your requestBody\n (or legacy position within the requestBody schema)\n to override the name of the parameter that will be passed to your\n handler function.\n\n.. code-block:: yaml\n\n\n /path\n post:\n requestBody:\n x-body-name: body\n content:\n application/json:\n schema:\n # legacy location here should be ignored because the preferred location for x-body-name is at the requestBody level above\n x-body-name: this_should_be_ignored\n $ref: '#/components/schemas/someComponent'\n\n.. warning:: When you define a parameter at your endpoint as *not* required, and\n this argument does not have default value in your Python view, you will get\n a \"missing positional argument\" exception whenever you call this endpoint\n WITHOUT the parameter. Provide a default value for a named argument or use\n ``**kwargs`` dict.\n\nType casting\n^^^^^^^^^^^^\n\nWhenever possible, Firetail will try to parse your argument values and\ndo type casting to related Python native values. The current\navailable type castings are:\n\n+--------------+-------------+\n| OpenAPI Type | Python Type |\n+==============+=============+\n| integer | int |\n+--------------+-------------+\n| string | str |\n+--------------+-------------+\n| number | float |\n+--------------+-------------+\n| boolean | bool |\n+--------------+-------------+\n| array | list |\n+--------------+-------------+\n| null | None |\n+--------------+-------------+\n| object | dict |\n+--------------+-------------+\n\nIf you use the ``array`` type In the Swagger definition, you can define the\n``collectionFormat`` so that it won't be recognized. FireTail currently\nsupports collection formats \"pipes\" and \"csv\". The default format is \"csv\".\n\nFireTail is opinionated about how the URI is parsed for ``array`` types.\nThe default behavior for query parameters that have been defined multiple\ntimes is to use the right-most value. For example, if you provide a URI with\nthe the query string ``?letters=a,b,c&letters=d,e,f``, FireTail will set\n``letters = ['d', 'e', 'f']``.\n\nYou can override this behavior by specifying the URI parser in the app or\napi options.\n\n.. code-block:: python\n\n from firetail.decorators.uri_parsing import AlwaysMultiURIParser\n options = {'uri_parser_class': AlwaysMultiURIParser}\n app = firetail.App(__name__, specification_dir='swagger/', options=options)\n\nYou can implement your own URI parsing behavior by inheriting from\n``firetail.decorators.uri_parsing.AbstractURIParser``.\n\nThere are a handful of URI parsers included with connection.\n\n+----------------------+---------------------------------------------------------------------------+\n| OpenAPIURIParser | This parser adheres to the OpenAPI 3.x.x spec, and uses the ``style`` |\n| default: OpenAPI 3.0 | parameter. Query parameters are parsed from left to right, so if a query |\n| | parameter is defined twice, then the right-most definition will take |\n| | precedence. For example, if you provided a URI with the query string |\n| | ``?letters=a,b,c&letters=d,e,f``, and ``style: simple``, then FireTail |\n| | will set ``letters = ['d', 'e', 'f']``. For additional information see |\n| | `OpenAPI 3.0 Style Values`_. |\n+----------------------+---------------------------------------------------------------------------+\n| Swagger2URIParser | This parser adheres to the Swagger 2.0 spec, and will only join together |\n| default: OpenAPI 2.0 | multiple instance of the same query parameter if the ``collectionFormat`` |\n| | is set to ``multi``. Query parameters are parsed from left to right, so |\n| | if a query parameter is defined twice, then the right-most definition |\n| | wins. For example, if you provided a URI with the query string |\n| | ``?letters=a,b,c&letters=d,e,f``, and ``collectionFormat: csv``, then |\n| | FireTail will set ``letters = ['d', 'e', 'f']`` |\n+----------------------+---------------------------------------------------------------------------+\n| FirstValueURIParser | This parser behaves like the Swagger2URIParser, except that it prefers |\n| | the first defined value. For example, if you provided a URI with the query|\n| | string ``?letters=a,b,c&letters=d,e,f`` and ``collectionFormat: csv`` |\n| | then FireTail will set ``letters = ['a', 'b', 'c']`` |\n+----------------------+---------------------------------------------------------------------------+\n| AlwaysMultiURIParser | This parser is backwards compatible with FireTail 1.x. It joins together |\n| | multiple instances of the same query parameter. |\n+----------------------+---------------------------------------------------------------------------+\n\n\nParameter validation\n^^^^^^^^^^^^^^^^^^^^\n\nFireTail can apply strict parameter validation for query and form data\nparameters. When this is enabled, requests that include parameters not defined\nin the swagger spec return a 400 error. You can enable it when adding the API\nto your application:\n\n.. code-block:: python\n\n app.add_api('my_apy.yaml', strict_validation=True)\n\nAPI Versioning and basePath\n---------------------------\n\nSetting a base path is useful for versioned APIs. An example of\na base path would be the ``1.0`` in `` https://MYHOST/1.0/hello_world``.\n\nIf you are using OpenAPI 3.x.x, you set your base URL path in the\nservers block of the specification. You can either specify a full\nURL, or just a relative path.\n\n.. code-block:: yaml\n\n servers:\n - url: https://MYHOST/1.0\n description: full url example\n - url: /1.0\n description: relative path example\n\n paths:\n ...\n\nIf you are using OpenAPI 2.0, you can define a ``basePath`` on the top level\nof your OpenAPI 2.0 specification.\n\n.. code-block:: yaml\n\n basePath: /1.0\n\n paths:\n ...\n\nIf you don't want to include the base path in your specification, you\ncan provide it when adding the API to your application:\n\n.. code-block:: python\n\n app.add_api('my_api.yaml', base_path='/1.0')\n\nSwagger JSON\n------------\nFireTail makes the OpenAPI/Swagger specification in JSON format\navailable from either ``swagger.json`` (for OpenAPI 2.0) or\n``openapi.json`` (for OpenAPI 3.x.x) at the base path of the API.\nFor example, if your base path was ``1.0``, then your spec would be\navailable at ``/1.0/openapi.json``.\n\nYou can disable serving the spec JSON at the application level:\n\n.. code-block:: python\n\n options = {\"serve_spec\": False}\n app = firetail.App(__name__, specification_dir='openapi/',\n options=options)\n app.add_api('my_api.yaml')\n\nYou can also disable it at the API level:\n\n.. code-block:: python\n\n options = {\"serve_spec\": False}\n app = firetail.App(__name__, specification_dir='openapi/')\n app.add_api('my_api.yaml', options=options)\n\nHTTPS Support\n-------------\n\nWhen specifying HTTPS as the scheme in the API YAML file, all the URIs\nin the served Swagger UI are HTTPS endpoints. The problem: The default\nserver that runs is a \"normal\" HTTP server. This means that the\nSwagger UI cannot be used to play with the API. What is the correct\nway to start a HTTPS server when using FireTail?\n\nOne way, `described by Flask`_, looks like this:\n\n.. code-block:: python\n\n from OpenSSL import SSL\n context = SSL.Context(SSL.SSLv23_METHOD)\n context.use_privatekey_file('yourserver.key')\n context.use_certificate_file('yourserver.crt')\n\n app.run(host='127.0.0.1', port='12344',\n debug=False/True, ssl_context=context)\n\nHowever, FireTail doesn't provide an ssl_context parameter. This is\nbecause Flask doesn't, either--but it uses ``**kwargs`` to send the\nparameters to the underlying `werkzeug`_ server.\n\nThe Swagger UI Console\n----------------------\n\nThe Swagger UI for an API is available through pip extras.\nYou can install it with ``pip install firetail[swagger-ui]``.\nIt will be served up at ``{base_path}/ui/`` where ``base_path`` is the\nbase path of the API.\n\nYou can disable the Swagger UI at the application level:\n\n.. code-block:: python\n\n app = firetail.App(__name__, specification_dir='openapi/',\n options={\"swagger_ui\": False})\n app.add_api('my_api.yaml')\n\n\nYou can also disable it at the API level:\n\n.. code-block:: python\n\n app = firetail.App(__name__, specification_dir='openapi/')\n app.add_api('my_api.yaml', options={\"swagger_ui\": False})\n\nIf necessary, you can explicitly specify the path to the directory with\nswagger-ui to not use the firetail[swagger-ui] distro.\nIn order to do this, you should specify the following option:\n\n.. code-block:: python\n\n options = {'swagger_path': '/path/to/swagger_ui/'}\n app = firetail.App(__name__, specification_dir='openapi/', options=options)\n\nIf you wish to provide your own swagger-ui distro, note that FireTail\nexpects a jinja2 file called ``swagger_ui/index.j2`` in order to load the\ncorrect ``swagger.json`` by default. Your ``index.j2`` file can use the\n``openapi_spec_url`` jinja variable for this purpose:\n\n.. code-block::\n\n const ui = SwaggerUIBundle({ url: \"{{ openapi_spec_url }}\"})\n\nAdditionally, if you wish to use swagger-ui-3.x.x, it is also provided by\ninstalling firetail[swagger-ui], and can be enabled like this:\n\n.. code-block:: python\n\n from swagger_ui_bundle import swagger_ui_3_path\n options = {'swagger_path': swagger_ui_3_path}\n app = firetail.App(__name__, specification_dir='swagger/', options=options)\n\n\nServer Backend\n--------------\n\nBy default FireTail uses the Flask_ server. For asynchronous\napplications, you can also use Tornado_ as the HTTP server. To do\nthis, set your server to ``tornado``:\n\n.. code-block:: python\n\n import firetail\n\n app = firetail.App(__name__, specification_dir='swagger/')\n app.run(server='tornado', port=8080)\n\nYou can use the Flask WSGI app with any WSGI container, e.g. `using\nFlask with uWSGI`_ (this is common):\n\n.. code-block:: python\n\n app = firetail.App(__name__, specification_dir='swagger/')\n application = app.app # expose global WSGI application object\n\n\nSet up and run the installation code:\n\n.. code-block:: bash\n\n $ sudo pip3 install uwsgi\n $ uwsgi --http :8080 -w app -p 16 # use 16 worker processes\n\nSee the `uWSGI documentation`_ for more information.\n\n.. _using Flask with uWSGI: https://flask.pocoo.org/docs/latest/deploying/uwsgi/\n.. _uWSGI documentation: https://uwsgi-docs.readthedocs.org/\n\n\nDocumentation\n=============\nAdditional information is available at `FireTail's Documentation Page`_.\n\nChanges\n=======\n\nA full changelog is maintained on the `GitHub releases page`_.\n\n.. _GitHub releases page: https://github.com/FireTail-io/firetail-py-lib/releases\n\nContributing to FireTail/TODOs\n================================\n\nWe welcome your ideas, issues, and pull requests. Just follow the\nusual/standard GitHub practices.\n\nUnless you explicitly state otherwise in advance, any non trivial\ncontribution intentionally submitted for inclusion in this project by you\nto the steward of this repository (Point Security Inc DBA FireTail (TM)) shall be under the\nterms and conditions of Lesser General Public License 2.0 written below, without any\nadditional copyright information, terms or conditions.\n\nTODOs\n-----\n\n\n\nLicense\n===================\n\nCopyright 2022 Point Security Inc DBA FireTail (TM)\n\nLicensed under the Lesser General Public License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.gnu.org/licenses/lgpl-3.0.txt.\n\nUnless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.\n\n\n",
"bugtrack_url": null,
"license": "LGPLv3",
"summary": "Firetail - API first applications with OpenAPI/Swagger and Flask",
"version": "1.1.0",
"project_urls": {
"Homepage": "https://github.com/FireTail-io/firetail-py-lib"
},
"split_keywords": [
"openapi",
"oai",
"swagger",
"rest",
"api",
"oauth",
"flask",
"microservice",
"framework"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "003da15d7a8849ac13559b8566980d61666cfcc0ec9b80f931e4b724f3720061",
"md5": "c00061cc4975303c917d386b15749e1b",
"sha256": "d94eafed601b18e8d275c64bc7e154145d9b9d76a688ae55534e0a7317c251e4"
},
"downloads": -1,
"filename": "firetail-1.1.0-py2.py3-none-any.whl",
"has_sig": false,
"md5_digest": "c00061cc4975303c917d386b15749e1b",
"packagetype": "bdist_wheel",
"python_version": "py2.py3",
"requires_python": ">=3.6",
"size": 107210,
"upload_time": "2024-08-02T09:43:38",
"upload_time_iso_8601": "2024-08-02T09:43:38.473307Z",
"url": "https://files.pythonhosted.org/packages/00/3d/a15d7a8849ac13559b8566980d61666cfcc0ec9b80f931e4b724f3720061/firetail-1.1.0-py2.py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "40c415b97397f583e488cee99ea8e83f3d5fa9e07dc60870e71f458bdd48ab1c",
"md5": "0670762c366dcacc07c539fe1d063e9c",
"sha256": "bb5615bb0073d67ccae04cd079dc86aad7c8f70b4bacd88eab1d7546692bb31e"
},
"downloads": -1,
"filename": "firetail-1.1.0.tar.gz",
"has_sig": false,
"md5_digest": "0670762c366dcacc07c539fe1d063e9c",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.6",
"size": 94158,
"upload_time": "2024-08-02T09:43:40",
"upload_time_iso_8601": "2024-08-02T09:43:40.572268Z",
"url": "https://files.pythonhosted.org/packages/40/c4/15b97397f583e488cee99ea8e83f3d5fa9e07dc60870e71f458bdd48ab1c/firetail-1.1.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-08-02 09:43:40",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "FireTail-io",
"github_project": "firetail-py-lib",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [
{
"name": "a2wsgi",
"specs": [
[
"==",
"1.4"
]
]
},
{
"name": "clickclick",
"specs": [
[
"==",
"1.2"
]
]
},
{
"name": "flask",
"specs": [
[
"==",
"2.2.5"
]
]
},
{
"name": "inflection",
"specs": [
[
"==",
"0.3.1"
]
]
},
{
"name": "jsonschema",
"specs": [
[
"==",
"4.0.1"
]
]
},
{
"name": "PyJWT",
"specs": [
[
"==",
"2.4.0"
]
]
},
{
"name": "PyYAML",
"specs": [
[
"==",
"6.0.1"
]
]
},
{
"name": "requests",
"specs": [
[
"==",
"2.31.0"
]
]
},
{
"name": "starlette",
"specs": [
[
"==",
"0.27.0"
]
]
},
{
"name": "werkzeug",
"specs": [
[
"==",
"2.2.3"
]
]
},
{
"name": "swagger-ui-bundle",
"specs": [
[
"==",
"0.0.9"
]
]
},
{
"name": "aiohttp_jinja2",
"specs": []
},
{
"name": "aiohttp",
"specs": []
},
{
"name": "aiohttp_remotes",
"specs": []
},
{
"name": "pytest-aiohttp",
"specs": []
},
{
"name": "starlette",
"specs": []
},
{
"name": "a2wsgi",
"specs": []
},
{
"name": "packaging",
"specs": []
}
],
"tox": true,
"lcname": "firetail"
}
JSON
