policy module assumes global CONF object
Bug #1415626 reported by
Doug Hellmann
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oslo.policy |
Fix Released
|
High
|
Adam Young | ||
Bug Description
oslo_policy.policy assumes there is a global configuration object and modifies it on import. We have been moving away from that model with Oslo libraries, and instead requiring callers to pass a configuration object.
| Changed in oslo.policy: | |
| status: | New → Triaged |
| Changed in oslo.policy: | |
| milestone: | none → next-kilo |
| Changed in oslo.policy: | |
| assignee: | nobody → Adam Young (ayoung) |
Revision history for this message
| Ian Cordasco (icordasc) wrote | #1 |
| Changed in oslo.policy: | |
| status: | Triaged → Fix Committed |
| tags: | added: prerelease |
| Changed in oslo.policy: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I believe this was fixed in https:/