yahoo-eng-team team mailing list archive

[OpenStack Infra <1500509@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/263155
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=5fe12468cfd8445f7ebdd7d6ac940e2b4228a37c
Submitter: Jenkins
Branch:    master

commit 5fe12468cfd8445f7ebdd7d6ac940e2b4228a37c
Author: zhang.lei <zhang.lei@xxxxxxxxxxx>
Date:   Mon Jan 4 14:48:25 2016 +0800

    Define paste entrypoints
    
    Define filter factories so other projects can reference them by name
    and can take advantage of the python egg instead of referencing
    by the direct path.
    
    Change-Id: I8f2b409e35b44323ef1a4488de5964a0f1bd7cdc
    Closes-Bug: 1500509


** Changed in: keystone
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1500509

Title:
  Define paste entrypoints

Status in OpenStack Identity (keystone):
  Fix Released
Status in oslo.middleware:
  Fix Released

Bug description:
  oslo.middleware middlewares should define the entry points for the
  factories.

  In setup.cfg:

  [entry_points]
  paste.filter_factory =
      request_id = oslo_middleware:RequestId.factory

  (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#request_id

  So we'd change to "use = egg:oslo.middleware#request_id".

  And then eventually we can remove the line from keystone-paste.ini.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1500509/+subscriptions