Tracker #29939
closed
Improve setting definition DSL and move setting registry to memory
Added by Ondřej Ezr over 4 years ago.
Updated almost 2 years ago.
Description
Currently we have all the settings (both changed and unchanged) in the database, but we have all the defaults in code as well, so it makes no sense to have quite a heavy code base to keep both in sync.
Instead I'd like to bring the setting inventory into memory and database would keep only the changed settings.
It should give as an easy way for plugins to extend settings category not just adding a new one.
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7702 added
- Related to Refactor #30354: Use only public setting interface to update setting values added
- Target version changed from 2.2.0 to 2.3.0
- Subject changed from Add extension point to setting defaults to Move setting registry into a memory
- Description updated (diff)
- Tracker changed from Feature to Tracker
- % Done set to 0
- Pull request deleted (
https://github.com/theforeman/foreman/pull/7702)
- Description updated (diff)
- Target version changed from 2.3.0 to 2.4.0
- Target version deleted (
2.4.0)
- Target version set to 2.5.0
- Subject changed from Move setting registry into a memory to Improve setting definition DSL and move setting registry to memory
- Blocks Refactor #32411: Remove the old Setting class, which now only holds helper methods added
- Target version deleted (
2.5.0)
- Related to Bug #33791: Settings defined in settings.yaml do not take precedence in the new DSL added
- Fixed in Releases 3.6.0 added
- Status changed from Ready For Testing to Closed
- % Done changed from 95 to 100
Also available in: Atom
PDF