Another hack would be to have a ssh config and ansible config per vpc. The
ansible config points to the appropriate ssh config for the vpc, which
contains the correct bastion ip for said vpc, otherwise the files are the
same.
ie. ansible-vpc1.cfg / ssh-vpc1.cfg
ansible-vpc2.cfg / ssh-vpc2.cfg
Then start the playbook as:
$ export ANSIBLE_CONFIG=$(pwd)/ansible-vpc1.cfg && ansible-playbook
playbook.yml
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/0ee9edda-103c-4f98-a314-2469a7f752af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
