| commit | 5bb8a33c73eb418729227e071af6777703913a65 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Thu Jun 23 17:41:33 2022 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Thu Jun 30 15:55:44 2022 +0000 |
| tree | 243c70849397b0a708864eb2b7a3d02ec5d41f4e | |
| parent | b43d0f0765916e029db8f784e44659fc8468e945 [diff] [blame] |
m/t/launch: use cluster resolver This makes the cluster launch framework use a resolver to connect to cluster nodes after credential escrow has been performed. Change-Id: I09b0ec50bdb758e0c91e505a3c51839bb274f959 Reviewed-on: https://review.monogon.dev/c/monogon/+/797 Tested-by: Jenkins CI Reviewed-by: Lorenz Brun <lorenz@monogon.tech>
diff --git a/metropolis/test/launch/cluster/BUILD.bazel b/metropolis/test/launch/cluster/BUILD.bazel index 54e6a46..a0e82b4 100644 --- a/metropolis/test/launch/cluster/BUILD.bazel +++ b/metropolis/test/launch/cluster/BUILD.bazel
@@ -22,6 +22,7 @@ "//metropolis/node", "//metropolis/node/core/identity", "//metropolis/node/core/rpc", + "//metropolis/node/core/rpc/resolver", "//metropolis/pkg/logbuffer", "//metropolis/proto/api", "//metropolis/proto/common",