From 45fa4e0a7cec66acb98db26df52a60befc3f8179 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jos=C3=A9=20Lorenzo=20Rodr=C3=ADguez?= Date: Fri, 3 Aug 2018 16:03:28 +0200 Subject: [PATCH] Setting the status to passing for rebooting rds instances Instances do not become unavailable in the seconds the status changes to rebooting, so de-registering the service from consul can actually be more harm that worth. Additionally, if the RDS instance is configured with Multi-AZ failover, rebooting the instance should actaully never mean a change in the passing status of the service. --- service/rds/writer.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/service/rds/writer.go b/service/rds/writer.go index 3776f44..c6e3e29 100644 --- a/service/rds/writer.go +++ b/service/rds/writer.go @@ -127,7 +127,7 @@ func (r *RDS) writeBackendCatalog(instance *config.DBInstance, logger *log.Entry case "failed": status = "critical" case "rebooting": - status = "critical" + status = "passing" case "renaming": status = "critical" case "restore-error":