arcbox-connect 0.6.3

Connect RPC surface for the ArcBox sandbox API (connectrpc + buffa)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78

//! Build script for the ArcBox Connect RPC surface.
//!
//! Generates buffa message types plus ConnectRPC service traits and clients
//! for every ArcBox-owned proto (`arcbox.v1` and `arcbox.sandbox.v1`).
//! These types serve the daemon's client-facing Connect surface and both
//! ends of the host↔guest vsock wire (CORE-73). Remaining prost consumers
//! of the same protos interoperate byte-for-byte: buffa and prost emit
//! identical protobuf bytes from the same `.proto` sources.

fn main() {
    let proto_dir = "../arcbox-protocol/proto";

    let protos = [
        // The daemon's own surface (CORE-68). These all share one `arcbox.v1`
        // package, so message generation is all-or-nothing here even though
        // the services move onto Connect one at a time. `common.proto` must be
        // listed explicitly: it defines this package's hand-rolled `Timestamp`
        // and `Mount`, which are NOT the well-known types.
        "common.proto",
        "machine.proto",
        "macos.proto",
        "container.proto",
        "image.proto",
        "agent.proto",
        "api.proto",
        "kubernetes.proto",
        "stats.proto",
        "arcbox/sandbox/v1/sandbox.proto",
        "arcbox/sandbox/v1/process.proto",
        "arcbox/sandbox/v1/filesystem.proto",
        "arcbox/sandbox/v1/snapshot.proto",
        "arcbox/sandbox/v1/template.proto",
        "arcbox/sandbox/v1/errors.proto",
    ];

    // Run protoc ourselves and hand connectrpc-build the descriptor set:
    // its own protoc invocation cannot pass extra flags, and the older
    // protoc still found on some CI runners requires
    // --experimental_allow_proto3_optional (newer versions ignore it) —
    // the same compatibility stance as arcbox-protocol/build.rs. Binary
    // discovery mirrors connectrpc-build: $PROTOC, else PATH.
    let out_dir = std::path::PathBuf::from(std::env::var_os("OUT_DIR").expect("OUT_DIR unset"));
    let descriptor = out_dir.join("arcbox_connect.protoset");
    let protoc = std::env::var("PROTOC").unwrap_or_else(|_| "protoc".to_string());
    let status = std::process::Command::new(&protoc)
        .arg("--experimental_allow_proto3_optional")
        .arg("--include_imports")
        .arg("--include_source_info")
        .arg(format!("--descriptor_set_out={}", descriptor.display()))
        .arg(format!("--proto_path={proto_dir}"))
        .args(protos)
        .status()
        .unwrap_or_else(|e| panic!("failed to invoke {protoc}: {e}"));
    assert!(
        status.success(),
        "protoc failed building the Connect descriptor set"
    );

    // Precompiled mode emits no rerun directives for the sources; declare
    // them so a proto edit regenerates.
    for proto in protos {
        println!("cargo:rerun-if-changed={proto_dir}/{proto}");
    }

    connectrpc_build::Config::new()
        .files(&protos)
        .descriptor_set(&descriptor)
        .emit_rerun_directives(false)
        .include_file("_connectrpc.rs")
        .generate_json(true)
        // `arcbox.v1` files sit at the proto root rather than in `arcbox/v1/`
        // (the PACKAGE_DIRECTORY_MATCH violation `buf lint` already reports),
        // so without this the generator emits one module per file and
        // intra-package references do not resolve.
        .file_per_package(true)
        .compile()
        .expect("Failed to compile protos for Connect");
}