Tracker #29939
Improve setting definition DSL and move setting registry to memory
% Done:
100%
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.
Subtasks
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot over 2 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7702 added
#2
Updated by Ondřej Ezr over 2 years ago
- Related to Refactor #30354: Use only public setting interface to update setting values added
#3
Updated by Amit Upadhye over 2 years ago
- Target version changed from 2.2.0 to 2.3.0
#4
Updated by Ondřej Ezr over 2 years ago
- Subject changed from Add extension point to setting defaults to Move setting registry into a memory
#5
Updated by Ondřej Ezr over 2 years ago
- Description updated (diff)
#6
Updated by Ondřej Ezr over 2 years ago
- % Done set to 0
- Tracker changed from Feature to Tracker
- Pull request deleted (
https://github.com/theforeman/foreman/pull/7702)
#7
Updated by Ondřej Ezr over 2 years ago
- Description updated (diff)
#8
Updated by Ondřej Ezr over 2 years ago
- Related to Refactor #29257: remove x-editable-rails added
#9
Updated by Ondřej Ezr about 2 years ago
- Target version changed from 2.3.0 to 2.4.0
#10
Updated by Tomer Brisker about 2 years ago
- Target version deleted (
2.4.0)
#11
Updated by Amit Upadhye about 2 years ago
- Target version set to 2.5.0
#12
Updated by Ondřej Ezr almost 2 years ago
- Subject changed from Move setting registry into a memory to Improve setting definition DSL and move setting registry to memory
#13
Updated by Ondřej Ezr almost 2 years ago
- Blocks Refactor #32409: Use new DSL to define settings added
#14
Updated by Ondřej Ezr almost 2 years ago
- Blocks Refactor #32410: Use new DSL to define settings added
#15
Updated by Ondřej Ezr almost 2 years ago
- Blocks Refactor #32411: Remove the old Setting class, which now only holds helper methods added
#16
Updated by Ondřej Ezr almost 2 years ago
- Blocks Refactor #32412: Use new DSL to define settings added
#17
Updated by Ondřej Ezr almost 2 years ago
- Blocks Refactor #32413: Use new DSL to define settings added
#18
Updated by Ondřej Ezr almost 2 years ago
- Blocks Refactor #32414: Use new DSL to define settings added
#19
Updated by Ondřej Ezr almost 2 years ago
- Target version deleted (
2.5.0)
#20
Updated by Ondřej Ezr over 1 year ago
- Related to Bug #33791: Settings defined in settings.yaml do not take precedence in the new DSL added
#21
Updated by Ondřej Ezr 11 months ago
- Related to Refactor #34674: Use new DSL to define settings added
#22
Updated by Ondřej Ezr 8 months ago
- Related to Refactor #34677: Use new DSL to define settings added
#23
Updated by The Foreman Bot 19 days ago
- Fixed in Releases 3.6.0 added
#24
Updated by Ondřej Ezr 19 days ago
- % Done changed from 95 to 100
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|c791f6c70806952aef520cc779397560138f207e.
Fixes #29939 - drop category column from settings
Settings table was holding category column to support old style of
settings, but it is now ready to be decomissioned as plugins were given
enough time.