remoting API

As the popularity of bootc grows a central location for go types/examples would be useful for projects. Speaking with @cgwalters he is willing to consider something similar to rpmostree-client-go[1] for bootc but there is some intersection with [2].

Curious if instead of creating go client as a os exec wrapper, exposing some of the Rust functionality via CGO? Please include me in future conversations on the topic if possible 🙏 Wasmtime CGO examples as ref. [3],[4]. I understand that CGO is not ideal but in terms of interaction with Rust over FFI, I don't believe there is another option.

[1] https://github.com/coreos/rpmostree-client-go/
[2] https://github.com/containers/bootc/issues/518
[3] https://github.com/bytecodealliance/wasmtime/blob/b869b66bce8a57c9e83db4e3bcd6809d88e94a5f/crates/c-api/src/types/extern.rs#L39
[4] https://github.com/bytecodealliance/wasmtime-go/blob/cabc733f95623fb897b2c35266124192ffca94b4/externtype.go#L9C12-L9C29

Commencez par lire l’issue #518 associée de bootc, puis comparez rpmostree-client-go avec la Wasmtime C API liée et les exemples en Go. L’issue nécessite de définir le périmètre d’une Go API centrale, notamment de déterminer si elle doit encapsuler l’exécution de os ou exposer des fonctionnalités Rust via CGO ; le travail est terminé lorsqu’une approche est convenue et que l’API/les exemples sont définis.