I submitted a PR a month or so ago as a possible solution to specifying bastion hosts via an inventory variable:
Commented on Matt’s PR, but I think this is a good start.
I have also mentioned recently (today) that adding ansible_ssh_args as an inventory variable is also fine with me, to override what might be set in ansible.cfg.
i.e. let’s have both, if we want.
OK, PR 9477 implements bastion host/port/user/key and ssh_args as inventory vars…
Damn. I just thought of something.
How will “ansible -m ping <somewhere_behind_a_bastion_host>” work?
Hope I’ve overlooked something, but that could be a snag.
-T
Sorry for going dark on this thread- I had my notification settings for both GG and Github pointing at a dead work email.
I’m sure ping wouldn’t work on a private host out of the box, though I suspect you can probably get it working with delegate_to (or easily enhance it to work).
Np, Matt,
Ok. That makes sense.
Thanks,
-T
Matt, doesn’t this prevent you from using ec2 dynamic inventory? For me being unable to dynamically discover instances as they come and go in the VPC is huge limitation.