Describe the bug
When setting the ssh_command var with a destination port number, the command syntax is incorrect.
To Reproduce
Steps to reproduce the behavior:
- Deploy a config that provisions an environment including an
ssh command example for connecting to a specific port number, for example, a RHEL lab hosted on CNV.
- Observe that the
ssh_command var is set using ssh user@destination -p port syntax.
Expected behavior
Use correct ssh command syntax as found in OpenSSH documentation. This could be either:
- The traditional command syntax with options first followed by user@hostname destination, that is
ssh -p port user@destination, or
- The more modern way using a destination URI like
ssh ssh://user@hostname:port.
The URI syntax was introduced in 2018 with OpenSSH 7.7, so surely that should be good for everybody today.
Affected code
Additional context
My preference would be the more modern URI syntax, but happy to consider community input.
Unless there are any objections, I'll open a PR for this.
Describe the bug
When setting the
ssh_commandvar with a destination port number, the command syntax is incorrect.To Reproduce
Steps to reproduce the behavior:
sshcommand example for connecting to a specific port number, for example, a RHEL lab hosted on CNV.ssh_commandvar is set usingssh user@destination -p portsyntax.Expected behavior
Use correct
sshcommand syntax as found in OpenSSH documentation. This could be either:ssh -p port user@destination, orssh ssh://user@hostname:port.The URI syntax was introduced in 2018 with OpenSSH 7.7, so surely that should be good for everybody today.
Affected code
Additional context
My preference would be the more modern URI syntax, but happy to consider community input.
Unless there are any objections, I'll open a PR for this.