Closed Bug 1250211 Opened 9 years ago Closed 8 years ago

Allow localconfig to override (force) certain data/params values

Categories

(Bugzilla :: Installation & Upgrading, enhancement)

Product:
Bugzilla
Component:
Installation & Upgrading
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: dylan, Assigned: dylan)

References

Details

+++ This bug was initially created as a clone of Bug #1218457 +++ I think this would be useful for other bugzilla installs. It would require documenting which params can be overridden -- or a more general solution where we ensure that the overridden version isn't written back out to data/params.json. Discussion encouraged.
(In reply to Dylan William Hardison [:dylan] from comment #0) > I think this would be useful for other bugzilla installs. This is a bit vague. Useful for which purposes? And why defining the same parameters in two different files? To encourage discussion, we would need the reasoning for this feature. :)
Severity: normal → enhancement
Component: Bugzilla-General → Installation & Upgrading
This won't be the solution we go for. The initial problem was a conflict between ops and devs on who owns data/params. Things like db servers and memcached are configured in data/params. I think a better solution is for those things to be configured in localconfig
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.