Merge ~cjwatson/ols-charm-deps:wsgi-restart-on-version-info-change into ols-charm-deps:master
Proposed by
Colin Watson
Status: | Merged |
---|---|
Approved by: | Colin Watson |
Approved revision: | 0dd1c199056a0d678a4dc99703c7d70dd00b1c53 |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~cjwatson/ols-charm-deps:wsgi-restart-on-version-info-change |
Merge into: | ols-charm-deps:master |
Diff against target: |
65 lines (+12/-2) 4 files modified
layer/ols-wsgi/reactive/ols_wsgi.py (+2/-1) layer/ols/lib/ols/base.py (+4/-0) layer/ols/reactive/ols.py (+2/-1) layer/ols/unit_tests/test_ols.py (+4/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Guillermo Gonzalez | Approve | ||
Review via email: mp+381747@code.launchpad.net |
Commit message
Restart gunicorn if version-info.txt changes
Description of the change
If we're in symlink-switch mode, then we need to restart gunicorn when a new payload has been deployed; but this may not correspond to any of the configuration changes that ols-wsgi detects. Since services generally want to ship a version-info.txt anyway, add that to the list of files that trigger a hard restart if they're changed.
To post a comment you must log in.
+1
nice way to handle it