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

DIff email #109

Open
earicmartin opened this issue Jul 22, 2019 · 8 comments
Open

DIff email #109

earicmartin opened this issue Jul 22, 2019 · 8 comments

Comments

@earicmartin
Copy link

Hello,

Was wondering would it be hard to add auto diff one each file every day and email if something is different.

@netniV
Copy link
Member

netniV commented Jul 23, 2019

I have something at work that does something like this. The issue is that it depends on knowing which lines to exlude from checking. For example, some systems update the timestamp at the top or bottom of the configuration, or the serial number changes if a failover event happens but the configuration is identical otherwise.

@earicmartin
Copy link
Author

Maybe put in if statement that can be filled in if someone wants to use it

@netniV
Copy link
Member

netniV commented Jul 24, 2019

It'd need several fields to handle it all but it's not a bad request 👍

@netniV
Copy link
Member

netniV commented Oct 2, 2019

I have given this some more thought and we would need to verify that the file was a text readable file not a binary one. We couldn't obviously compare a binary file properly.

@jdcoats
Copy link

jdcoats commented Jan 27, 2023

check out the latest develop and consider a daily diff email :)

@TheWitness
Copy link
Member

Well, that would be interesting. Not for this weekend though.

@jdcoats
Copy link

jdcoats commented Jan 27, 2023

understood... just a summary diff of each device post the scheduled run. note i said summary (diff and not sdiff) :)

@TheWitness
Copy link
Member

lol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants