You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Personally I do not understand this check. If the evn variable is required, you server will not just start and already will produce 502 or ConnectionRefused.
If the variable is there, then everything is started and no need to check anything. Am I missing something here?
@sshishov it's been quite a while since I opened this ticket, but I think what I was thinking was around the possibility of using Django-watchman as a check on a new deployment before cutting traffic over..
Deploy new code but don't send traffic yet
Manually or automatically use the watchman CLI on the new release to confirm everything is looking good (including expected env vars are set)
If good, begin rolling out new release - otherwise fail and alert about the bad deploy
Configure a list of environment variables to assert are set in
settings.py
.Should there be some default environment variables to check?
SECRET_KEY
WATCHMAN_TOKENS
The text was updated successfully, but these errors were encountered: