Question
Has anyone gotten Ansible 2.0 to work w/ the DigitalOcean v2 API?
- Posted on July 15, 2015
- APIDigitalOceanAnsibleConfiguration ManagementPython
Asked by limist
There seems to be a lack of well-documented examples of using the new Ansible 2.0 digital_ocean module to create DO droplets, using the v2 API. If anyone has done it, could you share a working code example please? Thanks!
Also posted more about this here: https://digitalocean.uservoice.com/forums/136585-digitalocean/suggestions/8883373-create-docs-for-ansible-2-0-do-v2-api
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Does anyone have ANY python library working with Digital Ocean?
After much trial and error on using Ansible modules with Digital Ocean, I thought I would post an update so that others don’t go down the same path and get as frustrated as I am.
Ansible/digital_ocean module As some instructions point out, you should use dopy 0.3.5. However, both ‘private_networking’ and ‘unique_name’ do not work. I didn’t thoroughly investigate, but it appears that a change in the API led to the breakage. I have found that if you use dopy 0.3.6, ‘private_networking’ was fixed, although I’m not sure if anything else was lost.
Ansible/digital_ocean_domain If you are creating a brand new domain record, this works. If the domain already exists and you use ‘state=present’, you will get an error. Looking at Github, it appears that a fix was submitted back in January, yet it sits unreviewed, going nowhere.
I’m pretty frustrated. I don’t know Python, but considering learning it now. And trying to think of some other solution to using Ansible with Digital Ocean. :(