-
-
Notifications
You must be signed in to change notification settings - Fork 11
Update Vultr API to v2 #17
Comments
Is there a list of anything missing between v1 and v2? |
Circling back to this after 5+ months. Any interest in this? ¯\_(ツ)_/¯ |
Thanks for bringing this up, I plan to start working beginning September with the transition to v2. btw, any sponsoring would help to stay motivated. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Please follow #22 for updates about implementation of the v2 API. |
Thank you very much for your contribution. In the meantime, Vultr has deprecated the v1 API and we have been working with @vultr to re-implement the modules with the v2 API. Therefore, this collection is now in maintenance mode and we encourage you to contribute new feature now here https://github.com/vultr/ansible-collection-vultr/. |
The Vultr v1 API is deprecated and it would be great to be able to use the v2 API.
https://www.vultr.com/news/Announcing-Vultr-API-v2/
The text was updated successfully, but these errors were encountered: