I am trying to use scaleway dynamic inventory plugin with scaleway module to manage cloud VPS farm.
The desired workflow is:
[inv:localhost] - add VPS host to scaleway via scaleway_compute module (state: running, wait: yes)
[inv:scaleway] - control just added host which must be listed by the scaleway inventory plugin (with proper state: running or, perhaps, stopped)
The problem is that scaleway inventory lists only hosts which have region set (ams1 or par1), other are treated as “archived” and not listed.
But all hosts in stopped state do not have region defined, and are never listed.
Is it correct behaviour? The inventory listed hosts have “state: running” variable. But it means that state can’t be anything else since then the host will not be listed at all.
It does not look nice for me since after adding new host via scaleway_compute module (or with anything else - GUI, scw command line tool, etc), no one can know about it from scaleway inventory unless the host name is known in advance. As far as I understand, the purpose of any inventory is to list all hosts in a group. And then user can decide if those hosts are available (reachable or, say, have state: running or stopped, what can be used for filtering).
I can patch the scaleway inventory plugin to fix that. But first I wish to know if that was intentional for a reason. Does anyone use scaleway plugin and module to handle Scaleway cloud?