I can spin up the code and make it available. There is an example (highly-flask specific right now, but would be easy to make it generic) from keystone [0] has been implemented. Where should this code live? A new library? oslo.<something>? The aforementioned example would need "external middleware via config" loading capabilities, but that isn't hard to do, just adding an oslo.cfg opt and referencing it.
[0] https://github.com/openstack/keystone/blob/master/keystone/server/flask/core.py#L93 Cheers, --Morgan On Mon, Oct 22, 2018 at 8:12 AM Sean McGinnis <sean.mcgin...@gmx.com> wrote: > On Mon, Oct 22, 2018 at 07:49:35AM -0700, Morgan Fainberg wrote: > > I should be able to do a write up for Keystone's removal of paste *and* > > move to flask soon. > > > > I can easily extract the bit of code I wrote to load our external > > middleware (and add an external loader) for the transition away from > paste. > > > > I also think paste is terrible, and would be willing to help folks move > off > > of it rather than maintain it. > > > > --Morgan > > > > Do I detect a volunteer to champion a cycle goal? :) > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
