Closed TheSemicolons closed 1 year ago
@TheSemicolons thanks for reporting, investigating.
@TheSemicolons it seems that internal_ip
never worked in this inventory, are you referring to the ngine_io.vultr inventory?
The function was added by PR #87
fixed by #87
@resmo
I was using https://docs.ansible.com/ansible/latest/collections/vultr/cloud/vultr_inventory.html
and assumed that since the attributes
parameter linked to https://www.vultr.com/api/#operation/list-instances
that all those values were available for the compose
parameter.
I was attempting to do:
plugin: vultr.cloud.vultr
api_key: "[redacted]"
compose:
ansible_host: vultr_internal_ip or vultr_v6_main_ip or vultr_main_ip
keyed_groups:
- key: vultr_tags | lower
prefix: ''
separator: ''
strict: true
So that Ansible would manage instances over the internal_ip
instead of the v6_main_ip
or main_ip
.
Ok, thanks for clarification. I was wondering because you wrote "no longer shows up", but your example should be working with 1.10.0 released few hours ago.
Yup, working now with 1.10.0. I never used anything before 1.9.0, but since it was part of the API I assumed it worked at one point before.
Describe the bug When using
ansible-inventory --list
, theinternal_ip
no longer shows up in the instance data.To Reproduce
ansible-inventory --list
Expected behavior When an instance is attached to a VPC2.0, the "internal_ip" field should be populated.
Screenshots ansible.cfg:
vultr.yml
Desktop (please complete the following information where applicable:
Additional context
curl "https://api.vultr.com/v2/instances/[redacted]" -X GET -H "Authorization: Bearer [redacted]"
correctly shows the "internal_ip"