Define paste entrypoints
Bug #1500509 reported by
Brant Knudson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Wishlist
|
lei zhang | ||
oslo.middleware |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
oslo.middleware middlewares should define the entry points for the factories.
In setup.cfg:
[entry_points]
paste.filter_
request_id = oslo_middleware
(Or whatever you want to call the entrypoint)
Then we can use it in keystone instead of defining our own.
Here's how it's used in keystone:
[filter:request_id]
use = egg:keystone#
So we'd change to "use = egg:oslo.
And then eventually we can remove the line from keystone-paste.ini.
Changed in keystone: | |
importance: | Undecided → Wishlist |
description: | updated |
description: | updated |
Changed in oslo.middleware: | |
assignee: | nobody → Tom Cocozzello (tjcocozz) |
Changed in oslo.middleware: | |
status: | In Progress → Fix Released |
Changed in keystone: | |
assignee: | nobody → lei zhang (zhang-lei) |
To post a comment you must log in.
We need to be careful about staging the upgrade for this in keystone. The grenade tests should fail if keystone removes the entry point setting in its setup.cfg, but it should be possible to update the paste file and add an entry point to oslo.middleware in the same cycle, then remove the entry point from keystone in the next cycle.
However, it's not clear what paste will do when it finds multiple entry points with the same name. We should test that, maybe it will work fine, but if not we might need to use a different name for the same factory in oslo.middlware to avoid the conflict.