feat: implementation for opnsense os-node_exporter #173
No reviewers
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: NationTech/harmony#173
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feat/install_opnsense_node_exporter"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Added node_exporter to opnsense config and its implementation for OPNSenseFirewall
Could you make a quick screen recording (or screenshot) of this change in action? 📹
@ -0,0 +20,4 @@pub fn get_full_config(&self) -> &Option<NodeExporter> {&self.opnsense.opnsense.node_exporter}fn with_node_exporter<F, R>(&mut self, f: F) -> Rwhite line missing
@ -0,0 +27,4 @@match &mut self.opnsense.opnsense.node_exporter.as_mut() {Some(node_exporter) => f(node_exporter),None => unimplemented!("is it expected to have a line return here?
Looking good
@ -0,0 +10,4 @@}//TODO complete this implimpl std::fmt::Debug for dyn NodeExporter {I think we should leave it to the implementers to define their
Debugimpl. So on line 6 we should havepub trait NodeExporter: std::fmt::Debug + Send + Syncinstead.WIP: feat: implementation for opnsense os-node_exporterto feat: implementation for opnsense os-node_exporterCheckout
From your project repository, check out a new branch and test the changes.