Define PasteDeploy filter factories

[Tom Cocozzello]

Keystone middleware should define the entrypoints for the filter factories. This will help for other projects so they can take advantage of the python egg instead of having to reference their direct path.

The first thing that would need to be done is that the entry points would needed to be added to the setup.cfg

once that is done anyone it can be changed in the *paste.ini file for the projects and reference it using the python egg.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/233839

[David Stanek (dstanek)]

You'll probably have to wait on changing the *paste.ini files until after the global requirements are change to require at least the first version that will contain the entry points.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/233839
Committed: https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=63e7e662d336708eba476d5049c70b1d6f16b999
Submitter: Jenkins
Branch: master

commit 63e7e662d336708eba476d5049c70b1d6f16b999
Author: Tom Cocozzello <email address hidden>
Date: Mon Oct 12 16:15:07 2015 -0500

    Define entry points for filter factories for Paste Deployment

    Define filter factories so projects can reference them by name
    and can take advantage of the python egg instead of referencing
    by the direct path.

    Change-Id: I555ca5e4ae6bd89775d8ef95940b6915f4cef4da
    Closes-Bug: #1505407

[Doug Hellmann (doug-hellmann)]

This issue was fixed in openstack/keystonemiddleware 4.0.0 release.