If you can't use the Private IP address to reach the instance in question, then jump doesn't work.
I realise there are advantages to using the private network, but sometimes it's convenient to just use a Public IP address.
The implementation of this would be straightforward, but the real issue is the command line interface. Currently it's:
jump LEFT_ARGS ... -- RIGHT_ARGS ...
(with most bits being optional)
If we added a --public flag, say, then it would be:
jump --public LEFT_ARGS ... -- RIGHT_ARGS ...
I guess this is just about okay for one option that you probably don't want to pass to ssh, but when more options come along, we need to separate the options for jump from the options that are passed through to ssh.
So. We could:
- Make jump so that it had no configuration, no options.
- Terminate all
jump options with a required flag: jump --public -z LEFT_ARGS -- RIGHT_ARGS
- Configure
jump only by environment variables: JUMP_IP=public jump ...
or something else?
If you can't use the Private IP address to reach the instance in question, then
jumpdoesn't work.I realise there are advantages to using the private network, but sometimes it's convenient to just use a Public IP address.
The implementation of this would be straightforward, but the real issue is the command line interface. Currently it's:
(with most bits being optional)
If we added a
--publicflag, say, then it would be:I guess this is just about okay for one option that you probably don't want to pass to
ssh, but when more options come along, we need to separate the options forjumpfrom the options that are passed through tossh.So. We could:
jumpoptions with a required flag:jump --public -z LEFT_ARGS -- RIGHT_ARGSjumponly by environment variables:JUMP_IP=public jump ...or something else?