From 455003d0e924414db339395e8367166e7820c5da Mon Sep 17 00:00:00 2001
From: Alberto Sartori <alberto.sartori@huawei.com>
Date: Mon, 24 Feb 2025 14:16:42 +0100
Subject: just serve: allow clients to access execution endpoint with a
 different address

To properly use `just serve`, both the client and the serve instance
must talk to the very same execution endpoint. Typically, both the
client and serve can reach out to the execution endpoint via the same
IP address. However, it might be possible that the client and a serve
instance know the same execution endpoint by means of differnet IP
addresses. For example, the client knows the execution endpoint
address through an _external_ IP address, while the serve instance,
deployed within the same network infrastructure, only knows the
_internal_ IP address.

This patch adds the subkey `"client address"` -- of the key
`"execution endpoint"` -- in the serve configuration file, to specify
the alternative pair `address:port` used by the client.
---
 src/buildtool/common/cli.hpp | 2 ++
 1 file changed, 2 insertions(+)

(limited to 'src/buildtool/common/cli.hpp')

diff --git a/src/buildtool/common/cli.hpp b/src/buildtool/common/cli.hpp
index f486a5fd..ef6c043c 100644
--- a/src/buildtool/common/cli.hpp
+++ b/src/buildtool/common/cli.hpp
@@ -186,6 +186,8 @@ struct ServeArguments {
     std::optional<std::string> remote_serve_address;
     // repositories populated from just-serve config file
     std::vector<std::filesystem::path> repositories;
+    // remote execution endpoint as seen by the client
+    std::optional<std::string> client_remote_address;
 };
 
 struct GcArguments {
-- 
cgit v1.2.3