Hello,
we want to filter some hosts with the vSphere “Tags” (we use the vSphere-Module for director).
We can’t see them in the preview - is it a restriction of vsphere-api or the director module?
Background:
The sync always overwrites the hostgroup we’ve modified before the last sync.
We’ve different hostgroups for different usages.
Our idea is to split the import into several sync-jobs based on the vSphere-Tags.
@anon66228339 Thanks, we tried it with custom attributes instead of tags - like proposed in the issue. Unfortunately also these custom attributes are not visible in the importer.
The custom fields are at the moment developed into the module. There is a branch for that lab/customfields, but i would not recommend it to use in production.
Think this will come with one of the next versions, just be patience with @tgelf
I’ve seen the topic is already implemented as told here on 29 Apr 2020.
How could I make it available? Which version of whatever module do I need in my Icinga2 / Icingaweb2 (with director) test environment?
Would it be enough to get the latest vspheredb version?
… and if all requirements were met successfully, how could I expose a vcenter custom attribute to automation? Would it e.g. be available inside virtualization module previewing a host?