I just looked over ssh.py and ssh_old.py; if I were to actually want to
sit down and do this, I would factor those 2 classes, into a common base
class, then introduce a third version that supported ProxyCommand.
ps: I notice something odd in the two files above:
==
- def exec_command(self, cmd, tmp_path, sudo_user=None,
sudoable=False, executable='/bin/sh', in_data=None, su=False, su_user=None):
+ def exec_command(self, cmd, tmp_path, sudo_user=None,
sudoable=False, executable='/bin/sh', in_data=None, su_user=None, su=False):
==
Why is the order of the last 2 args reversed for those two files? Seems
like it might cause some confusion.
On 02/05/2014 01:51 PM, Adam Heath wrote:
I've had musings on that too. Currently, I think you'd have to manually
configure $HOME/.ssh/config, with ProxyCommand.
However, I just had a thought. What if there was an
ansible_ssh_proxy=$other_inventory_host feature? When set, ansible
would auto-add the -o ProxyCommand="$something".
This is just some random brainstorm ramblings.
On 02/05/2014 12:59 PM, Jeff Lord wrote:
Hello,
I am building out an env in AWS using ansible and would like to
configure all of my hosts by running through a single bastion host which
has port 22 open.
Laptop -> AWS Bastion -> AWS private network instances
Is there a good example of how to configure the proxy around?
Thank You in advance,
--
You received this message because you are subscribed to the Google Groups "Ansible
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
