Closed
Bug 1432569
Opened 8 years ago
Closed 8 years ago
Add python-based configuration source
Categories
(Socorro :: Backend, task)
Socorro
Backend
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: osmose, Assigned: osmose)
References
Details
We've been working to move configuration into Python code in several different places, such as the processor, signature generation, and crash storage systems. The main motivation is to have the behavioral configuration stored in code where it can be versioned, changed, and deployed more easily by developers.
I'd like to investigate adding a python module as a configuration source for Socorro, similar to a Django settings file. This module would be defined within the repo and versioned, and would be superseded by the environmental config values if they are present.
This bug covers the groundwork for setting a system like this up, and experimenting with using it in a few places in the site.
Comment 1•8 years ago
|
||
Commit pushed to master at https://github.com/mozilla-services/socorro
https://github.com/mozilla-services/socorro/commit/9294cb6d605527e30c69fa5075c04c6e62e98ee9
Bug 1432569: Remove SocorroWelcomeApp and scripts/socorro.
| Assignee | ||
Comment 2•8 years ago
|
||
The PR from comment 1 lands python-based default config for all Socorro apps, so this is pretty much resolved now.
When deploying this to staging and prod, we should be able to delete a bunch of unnecessary config values now. willkg has better methods for looking through the configs on these environments and has graciously offered to handle identifying and removing these config values.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•