private SlimeJsonResponse getDeploymentStatusV2(RestApi.RequestContext context) {
        Slime slime = new Slime();
        Cursor root = slime.setObject();
        Cursor inactiveDeploymentsArray = root.setArray("inactiveDeployments");
        curator.getChildren(DEPLOYMENT_STATUS_ROOT).stream()
               .filter(upstreamName -> deploymentStatus(upstreamName).status() == RoutingStatus.out)
               .sorted()
               .forEach(upstreamName -> {
                   Cursor deploymentObject = inactiveDeploymentsArray.addObject();
                   deploymentObject.setString("upstreamName", upstreamName);
               });
        root.setBool("zoneActive", zoneStatus() == RoutingStatus.in);
        return new SlimeJsonResponse(slime);
    }
This implements the /routing/v1/status REST API on the config server, providing explicit control over the routing
status of a deployment or zone (all deployments). The routing status manipulated by this is only respected by the
shared routing layer.

@author bjorncs
@author mpolden
configserver/src/main/java/com/yahoo/vespa/config/server/http/v1/RoutingStatusApiHandler.java