Integration with oxidized

[tonoitp]

I can imagine this running somewhere in the background.

Could be nice if it's triggered by t.ex. an config change in oxidized backup.
The changed config would be linted and output sent to syslog where it can be picked-up and send to irc/slack/SIEM whatever

[Kircheneer]

Thanks for submitting this. I have never used oxidized - can you elaborate a little as to what you except from this tool to make this integration possible?

[tonoitp]

oxidized is a backup tool that runs on a server and logs in periodically on (network) devices.
It downloads it's config, and if something has changed since last login, it will save that new config besides the previous ones.
Therefore it allows you to see the changes between any copies of a config it has stored.

[Kircheneer]

Looking at the oxidized documentation it looks like this might already be possible with hooks. Can you verify this?

[tonoitp]

just started looking at that for a siem deployment. (might take a while due to other tasks at hand) but i keep you posted

[tonoitp]

well, that was bloody simple ;)
The hooks perfect easy to initiate the linting

ps: maybe slack, irc or the likes are better to chat/exchange info

[Kircheneer]

Do you care to show me how exactly you did this? I would like to throw it into the documentation somewhere.

[tonoitp]

--while running it dawned on me ... the last part can be done a lot easier, i re-write it after dinner--

[Kircheneer]

If you have the time, feel free to contribute some configuration/script to a contrib folder and write a little bit of documentation, I'm sure this is a use case more users would like to explore.

[Kircheneer]

Documentation is now online here if you want to take a look 👍

[tonoitp]

very neat! good job!