Block a user
feat: scaffold IoT walking skeleton — podman module, operator, and agent
Why is this not part of the full crd? Why add a bit more json into it after the fact? Am I missing something?
feat: scaffold IoT walking skeleton — podman module, operator, and agent
never write yaml. This must be typed rust. kube-rs provides all we need to declare a fully typed crd. Same goes for operator.yaml file.
refactor(iot): extract iot-contracts crate for cross-boundary types
podman is not iot specific. Podman belongs as a first-class citizen in harmony . Containers / containerruntime is a first class abstraction (I think it belongs in domain) and podman is either modules or infra. Definitely does not belong hidden in an iot crate.
refactor(iot): extract iot-contracts crate for cross-boundary types
feat: scaffold IoT walking skeleton — podman module, operator, and agent
Use args vec, more readable. Also true for all other Command::new calls.
feat: scaffold IoT walking skeleton — podman module, operator, and agent
This could very well use a harmony id from harmony_types. I like the id format, it is unique, relatively short and contains a timestamp.