Codey Oxley

I'm also in favor of this. Don't have a clear image of the required work here, but will try to make time for investigation unless @jathanism has already thought about...

I only have experience with one SSH terminal server (OpenGear), so I'm not sure the connection mechanic all of them use. OpenGear uses ports: `20xx/tcp`: Telnet lines `30xx/tcp`: SSH lines...

Yeah so from all of this, it appears `user:portid` is a much more common implementation for SSH console servers and I'd vote it's what we should support. Just a quick...

Agreed about compatibility. Would be nice if it was done in a way easy to phase out later vs having legacy shit in the codebase forever. I think this should...

:+1: I'm very for this as most places I've worked a local file wouldn't be good enough. I propose an authentication driver/loader. We can provide an `Authentication` `abc` driver where...

Leveraging NSoT hooks could apply here by distributing a small http server with Trigger to accept POST from NSoT device hooks and updating it's primary loader. My thinking is that...

Just an idea: Would be cool for each driver to have a property to contain its error conditions if they are pretty different from the standard ioslike/junos ones.

Since the CSV loader also uses the Rancid parser, this would prevent CSV files from providing device platform. Would either need to separate CSV parser or (easier and most likely)...

It would be trivial to do so, but currently there's no condition for the parsing. _parse_delimited_file() cares not what the delimeter actually is. Ref: https://github.com/trigger/trigger/blob/develop/trigger/rancid.py#L56

all those commits