[rancid] Run secondary login / collection script for entries in router.db? Anyone doing something like this?

[Howard Jones]

Probably easier to do it the other way around - collect it all in one
big swoop. The extra stuff is all done as comments anyway. And
postprocess those collected files into a second directory/file/repo
for the just-config parts.
On Tue, 2 Oct 2018 at 19:15, Ni Ne <nineoften at hotmail.com> wrote:
>
> I am curious to see the effort behind having the default configuration backup contain only the device configuration, and push other things like file system, interface status, inventory, etc, into a separate file. The main reason is I want to greatly increase the amount of ancillary data retrieved for each device, but don't want to clutter the configuration file itself, so disaster recovery is simpler.
>
> Is anyone doing this in a stream-lined fashion, where secondary login scripts are called for each device present in a router.db file? Ideally the administrator would only need to add a device once, and then based on vendor type that secondary login process would run transparently.
>
> I am still digging (back) into the RANCID internals to see how easy this would be to accomplish, so just curious if anyone is doing something like this already.
>
> Thanks!
>
> -Aaron
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss at shrubbery.net
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss