Striker invented its own system for non-executable configuration based on ini files providing values to interpolate into settings.py. This system is interesting, but also novel. https://pypi.org/project/django-environ/ can be used to provide similar functionality with less local magic. As a nice side effect, envvar based configuration is easier to reason about with a container based deployment.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| config: replace ini config with envvars | labs/striker | master | +300 -341 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | bd808 | T306469 Convert Striker to a container-based deployment | |||
| Resolved | Feature | bd808 | T306470 Replace ini config system with envvar config system |
Event Timeline
Comment Actions
It would actually be nice to have some period of supporting both ini and envvar based config, but it's probably easier from an implementation point of view to jump forward to envvar only.
Comment Actions
Change 784764 had a related patch set uploaded (by BryanDavis; author: Bryan Davis):
[labs/striker@master] config: replace ini config with envvars
Comment Actions
Change 784764 merged by jenkins-bot:
[labs/striker@master] config: replace ini config with envvars