inventory plugin uses vultr label to connect, rather than main_ip or hostname about ansible-collection-vultr

[gbot]

@resmo Thanks so much for the tip! Using compose works fine. I didn't realise that was possible to set directly in the inventory file. I just thought it was a bug because I couldn't see when you want the default behaviour - if the "label" is just set as arbitrary text labels on your Vultr account, Ansible will fail to connect.

[nschlemm]

@gbot thanks for filing this - stumbled over this as well ...
@resmo thanks for the compose hint, but I also support filing this as bug rather than a simple documentation issue as using the main_ip as default seems most sensible rather than an arbitrary text label ;)

[resmo]

Thanks @gbot for the report.

I don't think it's necessarily a bug, but certainly a documentation issue. We will look into it.
In the meantime, we suggest setting ansible_host with compose:

plugin: vultr.cloud.vultr
compose:
  ansible_host: vultr_main_ip

[resmo]

(issue got closed by accident merging #53, repoened)

I would like to briefly share my thoughts and concerns: defining ansible_host at host_vars level has a high prio in the ranking of variables.

In many probably most cases, main_ip would be the one users would want but if it should be possible to communicate via DNS resolve, SSH config (bastion host), VPN, inside Vultr VPC and via things I haven't thought of, this defaulting ansible_host could make things more complicated or limited.

Short, I am worried this default is not just a default but almost a hardcoded setting.

[resmo]

fixed by #53