From b0ebf22fb6de81bde5496566cb9544772d6d2da8 Mon Sep 17 00:00:00 2001
From: Thorarinn Sigurdsson <thorarinnsigurdsson@gmail.com>
Date: Tue, 17 Dec 2019 13:20:59 +0000
Subject: [PATCH] fix(core): use fresh statuses in get status cmd

Before this fix, the get status command was using force: false for its
GetServiceStatus tasks, which resulted in the overview tab of the
dashboard displaying stale service statuses.

After this fix, refreshing the dashboard once all services are deployed
will show their statuses as "ready", which is the expected/correct
behavior.
---
 garden-service/src/actions.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/garden-service/src/actions.ts b/garden-service/src/actions.ts
index f1de686dde..1c27639975 100644
--- a/garden-service/src/actions.ts
+++ b/garden-service/src/actions.ts
@@ -538,7 +538,7 @@ export class ActionRouter implements TypeGuard {
     const tasks = services.map(
       (service) =>
         new GetServiceStatusTask({
-          force: false,
+          force: true,
           garden: this.garden,
           graph,
           log,