Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oxidized-report-git-commits - how to stop triggering diff for uptime #1485

Closed
Kitesurfer0 opened this issue Aug 8, 2018 · 2 comments
Closed

Comments

@Kitesurfer0
Copy link

@Kitesurfer0 Kitesurfer0 commented Aug 8, 2018

diff --git a/saupar-acc04-c2950g b/saupar-acc04-c2950g
index 2c304be..f816693 100644
--- a/saupar-acc04-c2950g
+++ b/saupar-acc04-c2950g
@@ -6,7 +6,7 @@
! VTP: Compiled Fri 28-Jul-06 15:16 by weiliu
! VTP: Image text-base: 0x80010000, data-base: 0x8056A000
! VTP: ROM: Bootstrap program is C2950 boot loader
-! VTP: Drivers_uplink_level4 uptime is 3 days, 15 hours, 43 minutes
+! VTP: Drivers_uplink_level4 uptime is 3 days, 16 hours, 46 minutes
! VTP: System returned to ROM by power-on
! VTP: System restarted at 16:33:42 AEST Sun Aug 5 2018
! VTP: System image file is "flash:/c2950-i6q4l2-mz.121-22.EA8a.bin"

Should be an easy fix?

@systeembeheerder

This comment has been minimized.

Copy link
Contributor

@systeembeheerder systeembeheerder commented Sep 10, 2018

See https://github.com/ytti/oxidized/blob/master/docs/Configuration.md#removing-secrets

Guess you need something like

cfg.gsub! /^(VTP: Drivers_uplink_level4 uptime).*/, '\\1 <uptime removed>'

in the relevant model.rb. See https://github.com/ytti/oxidized/blob/master/docs/Creating-Models.md#extending-an-existing-model-with-a-new-command how to override/adjust the default.

@no-response

This comment has been minimized.

Copy link

@no-response no-response bot commented Oct 12, 2018

This issue has been automatically closed because there has been no response to our request for more information from the original author. The information that is currently in the issue is insufficient to take further action. Feel free to re-open this issue if additional information becomes available, or if you believe it has been closed in error.

@no-response no-response bot closed this Oct 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.