No values, we use full hydration. This will be handled by the rust binary generating a fully hydrated template, not typo magnets.
No yaml, a clusterrole is a fully typed rust struct with kube-rs, much more robust than typo-magnet templates.
No yaml. Use template hydration as specified in ADR 018. https://git.nationtech.io/NationTech/harmony/src/branch/master/docs/adr/018-Template-Hydration-For-Workload-Deployment.md
don't use yaml. Use rust structs and apply them directly. Even helm generation is fully hydrated, we only use helm as a packaging and versionning tool, no configuration.
This is potentially dangerous, what if we have multiple users on the same host? This is a tricky bit. Why to we need to know in advance what subuids podman expects? It feels like something that should be deferred to runtime/pod inspection once it is up. But I am lacking context to really understand the why here.
I strongly disagree with that. Not using helm here is bad but not because we love helm, much more so because we're introducing another unrelated method of doing the same thing instead of improving the tooling and robustness of what we already have. I think this whole nats_score_basic should be coupled in one way or another with the other nats scores we have.
a79c835b08
Merge pull request 'refactor(operator): replace gen-crd yaml pipeline with a harmony Score' (#271) from feat/install-reconcile-operator-score into feat/iot-walking-skeleton
8c94c8e61e
Merge pull request 'refactor(iot): extract iot-contracts crate for cross-boundary types' (#270) from feat/iot-contracts into feat/iot-walking-skeleton
4e787ddb71
Merge pull request 'feat/iot-arm-vm' (#269) from feat/iot-arm-vm into feat/iot-walking-skeleton
InstallTopology feels very unnatural.