-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add support for vultr api v2 #14587
base: master
Are you sure you want to change the base?
Conversation
👍 Worked well for me, thanks |
Waiting for it to be merged. Not sure if it will ever be 😂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This worked for me, thank you!
@@ -12,17 +12,21 @@ | |||
set_fact: | |||
algo_vultr_config: "{{ vultr_config | default(_vultr_config.user_input) | default(lookup('env','VULTR_API_CONFIG'), true) }}" | |||
|
|||
- name: Set the Vultr API Key as a fact | |||
set_fact: | |||
vultr_api_key: "{{ lookup('ansible.builtin.ini', 'key', section='default', file=algo_vultr_config) }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I reached the "Enter the local path to your configuration INI file" prompt, I left it blank in hopes it would use ~/.vultr.ini
by default, but I got an error:
"msg": "An unhandled exception occurred while running the lookup plugin 'ansible.builtin.ini'. Error was a <class 'ansible.errors.AnsibleParserError'>, original message: an error occurred while trying to read the file '/Users/max/dev/algo/roles/cloud-vultr/': [Errno 21] Is a directory:
I'm guessing it didn't like the empty input?
However, after entering ~/.vultr.ini
directly, everything worked for me
Thanks for the review! Please feel free to merge 🙂 |
@pentest01 @mkurapov Any plans to merge this and make a release? |
Hi, would love to see this released. |
I tried with this fork and still got the API error:
|
Sorry for my delay. Feel free to rebase and I'll review |
Will do it |
Description
Added support for Vultr Api v2 as new accounts on Vultr won't be able to use v1 api. Old accounts will be unable to use v1 api after June 2023.
Motivation and Context
This change makes sure AlgoVPN can be use by new and old users of Vultr
Fixes #14580
How Has This Been Tested?
Tested by Creating a VPS on Vultr with Ubuntu on my macbook m1
Types of changes
Checklist: