Project

General

Profile

Feature #2764

Override values in setting model from settings.yaml

Added by Dominic Cleal over 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
-
Category:
Settings
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

In the installer, we're beginning to use settings.yaml to populate settings in Foreman, rather than using foreman-config (because it's slow).

What we'd like is for values configured in settings.yaml to overwrite any values currently set in "Setting" records, while at the moment, the settings.yaml file is only used to initialise new settings (a kind of default value).

To prevent users getting confused, I'd expect the UI to prevent users from changing values set via settings.yaml and to inform them why the setting is "locked".

Associated revisions

Revision 4dbf6624 (diff)
Added by Dominic Cleal about 9 years ago

fixes #2764 - settings defined in settings.yaml file are now read-only

Revision 1370d8da (diff)
Added by Dominic Cleal about 9 years ago

fixes #2764 - settings defined in settings.yaml file are now read-only

(cherry picked from commit 4dbf662451f98c9bf9385cea4543a182d6ed7b8d)

History

#1 Updated by Lukas Zapletal over 9 years ago

  • Status changed from New to Assigned
  • Assignee set to Lukas Zapletal
  • Target version set to 1.3.0

We need this because of the proxy registration - taking.

#2 Updated by Lukas Zapletal over 9 years ago

  • Description updated (diff)
  • Assignee deleted (Lukas Zapletal)

Ok I need to close this browser tab for now :-)

#3 Updated by Dominic Cleal over 9 years ago

  • Status changed from Assigned to New

#4 Updated by Dominic Cleal over 9 years ago

  • Category set to Settings

#5 Updated by Lukas Zapletal over 9 years ago

  • Priority changed from Normal to Urgent

#6 Updated by Anonymous over 9 years ago

  • Assignee set to Anonymous
  • Status changed from New to Assigned

#7 Updated by Anonymous over 9 years ago

  • Status changed from Assigned to Ready For Testing

#9 Updated by Lukas Zapletal about 9 years ago

  • Priority changed from Urgent to Immediate

This is to be included in 1.3 final.

#10 Updated by Dominic Cleal about 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#11 Updated by Lukas Zapletal about 9 years ago

  • Related to Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final added

#12 Updated by Lukas Zapletal about 9 years ago

  • Related to deleted (Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final)

Also available in: Atom PDF