Open ellisgeek opened 2 years ago
Indeed, I've tested and confirmed this to be the case (it also broke one of my own playbooks that I run ever few months). Annoying that the attribute is now buried pretty deep, but I guess it's part of their push to make the networking for Droplets more robust / less public-IP-centric.
In Chapter 9 when setting up the digital ocean provisioner I ran into an issues with the task "Add DigitalOcean hosts to inventory groups." because the jinja template
"{{ item.1.data.ip_address }}"
was failing to return the ip of the droplet.It turns out this is because DO has changed their api a little bit and now returns a
networks
dict. See the stripped example json belowI did some digging and came up with the following.
Edit: I found #457 after making this and it looks like the solution there is more complete and it is indeed not fixed in version 1.14.