use config filter to hide internal option definitions from applications
Bug #1250737 reported by
Mark McLoughlin
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oslo.messaging |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
If oslo.messaging renames an option or moves it into a group (e.g. making rpc_backend to rpc.transport_
We do retain backwards compat for older user config files (i.e. even after a rename or move, the old values in config files still work) but we don't attempt to retain backwards compat in code.
In Icehouse, I really want to make it impossible for users of the library to use config options registered by the library. We need something like cfgfilter[1] to make it possible for oslo.messaging to register options with a ConfigOpts instance supplied by the user of the library ... without the user of the library seeing those options.
| Changed in oslo.messaging: | |
| milestone: | none → icehouse-2 |
| Changed in oslo.messaging: | |
| milestone: | icehouse-2 → icehouse-3 |
| Changed in oslo.messaging: | |
| assignee: | nobody → Mark McLoughlin (markmc) |
| Changed in oslo.messaging: | |
| milestone: | icehouse-3 → none |
Revision history for this message
| Doug Hellmann (doug-hellmann) wrote | #1 |
| summary: |
- oslo.messaging config options should not be used outside of the library + use config filter to hide internal option definitions from applications |
| Changed in oslo.messaging: | |
| importance: | High → Medium |
| assignee: | Mark McLoughlin (markmc) → nobody |
| Changed in oslo.messaging: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
The new config filter feature of oslo.config should make this possible.