Clarify the health checking logic and remove the accidental inclusion of the override
This commit is contained in:
parent
98602a2d0c
commit
aed7e67a17
1 changed files with 4 additions and 4 deletions
|
@ -49,8 +49,7 @@ class ProductionHealthCheck(HealthCheck):
|
||||||
def check_name(cls):
|
def check_name(cls):
|
||||||
return 'ProductionHealthCheck'
|
return 'ProductionHealthCheck'
|
||||||
|
|
||||||
def conduct_healthcheck(self, db_healthy, buildlogs_healthy):
|
def conduct_healthcheck(self, db_healthy, buildlogs_healthy):
|
||||||
db_healthy = False
|
|
||||||
data = {
|
data = {
|
||||||
'db_healthy': db_healthy,
|
'db_healthy': db_healthy,
|
||||||
'buildlogs_healthy': buildlogs_healthy
|
'buildlogs_healthy': buildlogs_healthy
|
||||||
|
@ -78,7 +77,8 @@ class ProductionHealthCheck(HealthCheck):
|
||||||
data['db_available_checked'] = True
|
data['db_available_checked'] = True
|
||||||
data['db_available_status'] = is_rds_working
|
data['db_available_status'] = is_rds_working
|
||||||
|
|
||||||
if is_rds_working:
|
# If RDS is down, then we still report the machine as healthy, so that it can handle
|
||||||
return (data, True)
|
# requests once RDS comes back up.
|
||||||
|
return (data, not is_rds_working)
|
||||||
|
|
||||||
return (data, db_healthy)
|
return (data, db_healthy)
|
Reference in a new issue