3a929611c0
Why limit a user to preset ssh arguments? Capture them all and send them along to ssh to deal with. This allows users to use the full range of ssh arguments, including specifying a command to run on the instance. For example: openstack server ssh -4 upg -- -l cirros -i ~/id_rsa_upg "date; uptime" SSH arguments that openstackclient currently mirrors are deprecated except for -4 and -6, as they are useful for retrieving the correct instance IP. Change-Id: Ia50786d5eee52688e180550fe16aeb8af610154b Co-authored-by: Stephen Finucane <stephen@that.guru>
15 lines
639 B
YAML
15 lines
639 B
YAML
---
|
|
features:
|
|
- |
|
|
Added the ability to pass arguments through to the ``ssh`` command When
|
|
using ``openstack server ssh``. This allows the user to use any ``ssh``
|
|
option without needing to add that option to the openstack client.
|
|
Existing openstackclient options that mirror SSH options are now
|
|
deprecated.
|
|
deprecations:
|
|
- |
|
|
``openstack server ssh`` options that mirror ``ssh`` options are now
|
|
deprecated (``--login, -l, --port, --identity, --option, -o, -vz``).
|
|
The ``ssh`` equivalent of each deprecated option should be used instead.
|
|
For example ``openstack server ssh instance -- -l user -i key``
|