Ansible feature request: Populate ansible.inventory_file with new IP address

[rdickert]

Hi, I love the new Ansible integration - this is the first time I've felt like it was easy enough to get a small bit of devops going, and it's really great.

One thing I'd love to see is a way to make new IP addresses available to Ansible so that automated provisioning can proceed. I'm developing small sites which deploy to either virtualbox or this digital_ocean provider. Because Ansible requires your IP host to be in the ansible_hosts file, all new hosts require an extra step of editing that file. For work on virtualbox, I can anticipate what that will be (127.0.0.1:2222), but on digital ocean, a new IP address is returned at runtime. If Vagrant could handle that step, I'd have an end-to-end process that I could share with other devs who like this approach. Right now, I don't see a way to make this work when you first provision. Of course, once I manually add the IP to my ansible_hosts, vagrant provision is working fine.

Thanks for your consideration, and thanks for Vagrant!

[mitchellh]

/cc @commandtab

[command-tab]

It's in the works, though it seems it will have to be on a per-VM basis. Multi-VM inventory (all in one file at run time, with ansible-playbook being called only once) will take a lot more work on the Vagrant side.

[rdickert]

Cool. A per-vm basis solution is all I need right now. I think people will get a lot of use out of that.

[bwghughes]

Hi @commandtab Any news on this - we're just doing some automated provisionsing on digitalocean and have hit the same skids - its hackable - but would rather it was part of the library.

[command-tab]

#1907 adds support for this :)

[rdickert]

Awesome! Thanks!

[mitchellh]

Fixed by #1907