a8411976a8
During peer stream replication we flatten checks from the source cluster and build one thin overall check to hide the irrelevant details from the consuming cluster. This flattening logic did correctly flip to non-passing if there were any non-passing checks, but WHICH status it got during that was random (warn/error). Also it didn't represent "maintenance" operations. There is an api package call AggregatedStatus which more correctly flattened check statuses. This PR replicated the more complete logic into the peer stream package. |
||
|---|---|---|
| .. | ||
| limiter | ||
| services | ||
| testutils | ||
| forward.go | ||
| options.go | ||
| options_test.go | ||
| server.go | ||
| stats_test.go | ||
| utils.go | ||