Ariel Barreiro

If interested in that, I can provide either a wider PR on this one, or a separate one if this is accepted as is.

I should also note that having this in ssh allows for bash/shell completion, which is pretty useful.

Just bumping this one, been using it so far pretty nicely, so if possible to be accepted great, so I don't have to use my fork for when I need...

@pjcdawkins just picking up on this, I rebased the commits and changed the writing of the configs into the already present config.yaml file.. relying entirely on CliConfig. Let me know...

I'll look into the code changes.. the reason I went for making the ports used persistent is because I thought that once you get your ssh config and your tunnels...

Oops, closed it accidentally.

In this particular command, maybe it's not that much of a big deal, I guess you could always output the same ports on the relationships and then edit it yourself...

@pjcdawkins well, for what it's worth, I changed for storing a state json file per command. Kind of what tunnel does, which could be refactor into using this same logic....

Just rebased the code on top of the latest changes.

I guess this PR could use a rebase, not sure if you are happy with merge commits with all intermediate ones or prefer to squash some.