Just a note: we already use add_host in the way Michael said. F.i. we first launch a EC2 instance, then add its public IP to the Ansible host file using add_host module: https://github.com/nimiq/ansible-biostar/blob/master/roles/ec2_instance/tasks/main.yml#L83
Paolo On Monday, 23 June 2014 18:17:51 UTC+2, Roman Valls wrote: > > Thanks Michael, > > I see, so you would go for the second option and implement the add_host > trick described here? Clever: > > http://skvidal.wordpress.com/2012/10/31/ansible-and-cloud-instances/ > > The inline extra-vars are meant to have things like aws_access_key and > other sensitive tokens away from potentially public version-controlled > files. > > In the future we might check if those are on, for instance, $HOME/.botorc > instead of having them in a .yml file in our playbook, just one commit away > from being published in the open. > > Thanks again! > Roman > > > Den måndagen den 23:e juni 2014 kl. 16:12:24 UTC+2 skrev Michael DeHaan: >> >> I'd probably keep the provisioning playbooks seperate and then have them >> include the configuration portion using the usual "add_host" handoff. >> >> Also I should point out >> >> --extra-vars @from_file.yml >> >> is an option >> >> >> >> >> On Mon, Jun 23, 2014 at 8:41 AM, Roman Valls <[email protected]> >> wrote: >> >>> Hello Ansible-Project, >>> >>> I would like to know which best practices are there when it comes to >>> deploying a playbook to several different cloud providers (mainly AWS and >>> GCE now, but more might come later). >>> >>> More specifically, which one feels more natural to you: >>> >>> ansible-playbook site.yml --extra-vars "cloud_provider=aws >>> aws_access_key=..." >>> ansible-playbook site.yml --extra-vars="cloud_provider=gce >>> gce_service_email=..." >>> >>> Which follows ansible docs on Best Practices... >>> >>> ... or the following, shorter version instead? >>> >>> ansible-playbook aws.yml --extra-vars "aws_access_key=..." >>> ansible-playbook gce.yml --extra-vars="gce_service_email=..." >>> >>> >>> >>> Here's the original GitHub discussion that triggered this email, thanks >>> Michael DeeHann for pointing this google group: >>> >>> https://github.com/nimiq/ansible-biostar/issues/11 >>> >>> Thanks in advance, >>> Roman >>> >>> -- >>> 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/73665fe0-d3c7-43aa-970b-e6de8a40f15b%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/ansible-project/73665fe0-d3c7-43aa-970b-e6de8a40f15b%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- 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/2cc26617-b954-4c59-9f55-5e0ef6bd281f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
