I haven't use this in anger for a while, so apologies if some of this functionality is already available, but how about:
- an option to disable compression of the config file - an option to specify the naming convention used - eg: always back up to a single file-name rather than appending the date and let your existing version control handle the diffs - checking it into git/subversion rather than just copying it to upstream folder (hey, a guy can dream) On 08/08/2013, at 5:25 AM, Phil Shafer <p...@juniper.net> wrote: >> 7 aug 2013 kl. 18:03 skrev Phil Mayers <p.may...@imperial.ac.uk>: >> Recently this fell apart on us, as the SSH key on the server changed and the >> archival >> transfers started to silently[1] fail. > > Ick. Silence is deadly. This (and the other issues) is now PR 910647. > >> All of which has me wondering if the feature is more trouble than it's worth. > > We definitely should be making it more robust and stable, but to > me the value of catching each commit as a distinct delta is a win. > It should also have the commit time, user, and commit comment, if > given. Having this in a repo means one can ask questions like "who > has changed config in my network since last Friday?" or "when did > this statement get added in the first place?". > > What else can we do to make this more worthwhile? > > Thanks, > Phil > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp