keystone/releasenotes/notes/bug-1776504-keystone-conversion-to-flask-372a5654a55675c6.yaml
Morgan Fainberg 184c84ae76 Remove pre-flask legacy code
This removes common.controller, common.extension, common.router, and
common.wsgi. Relevant code from common.wsgi (used by AuthContext) was
moved into keystone.server.flask.request_processing.middleware.auth_context.

keystone.api.discovery now uses keystone.flask.base_url

test_middleware and test_exception were modified to reflect the changes
to the remaining code from keystone.common.wsgi

keystone.common.authorization only holds a couple constants for auth
work now.

Routes is removed from requirements.txt

Release-Note for migration to flask added.

Change-Id: I81563b6a49c8f12ecade058a9483f3b6f070dc72
Closes-Bug: #1776504
2018-10-15 10:56:26 -07:00

27 lines
1.2 KiB
YAML

---
other:
- |
Keystone has been fully converted to run under flask. All of the APIs are
now natively dispatched under flask.
Included in this change is a removal of a legacy WSGI environment data
holder calld `openstack.params`. The data holder was used exclusively for
communicating data down the chain under paste-deploy. The data in
`openstack.params` was generally "normalized" in an odd way and
unreferenced in the rest of the openstack code-base.
Some minor changes to the JSON Home document occured to make it consistent
with the rest of our convensions (Technically an API contract break) but
required for the more strict view the Keystone flask code takes on setting
up the values for JSON Home. Notably "application_credentials" now has
an appropriate entry for listing and creating new app creds.
JSON Body and URL Normalizing middleware were move to a flask-native
model.
Any middleware defined in Keystone's tree is no longer loaded via
stevedore, and likewise the entry points were removed.
Original WSGI Framework (custom, home-rolled, based on WEBOB) has been
removed from the codebase.