Block a user
feat: implementation for opnsense os-node_exporter
I think we should leave it to the implementers to define their Debug impl. So on line 6 we should have pub trait NodeExporter: std::fmt::Debug + Send + Sync instead.
feat: implementation for opnsense os-node_exporter
Could you make a quick screen recording of this change in action? 📹
okd_enable_user_workload_monitoring
letian
pushed to okd_enable_user_workload_monitoring at NationTech/harmony
2025-10-21 13:48:35 +00:00
WIP: rook-ceph install score
fix(opnsense-config): ensure load balancer service configuration is idempotent
feat(application): Webapp feature with production dns
a quick cleanup/refactoring for this function could make things easier to read/understand, for example by breaking down the different steps into different (module private) functions
feat(application): Webapp feature with production dns
In addition to the comment above, I think it wouldn't be too tricky to refactor (if needed in another PR) with something like:
feat(application): Webapp feature with production dns
Does it have to be that specific? Or would it be ok if the signature was Result<Option<String>, Error> and that users of this function can decide what to do without values?

