-
Notifications
You must be signed in to change notification settings - Fork 8
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
Issues filtering import #17
Comments
Hi, I am having similar challenge. Have you setup a custom variable under the 'Data Fields' named 'vm_powerstate'? and what is the 'data type' you have used? Jay |
For me "vmstate=running" condition worked. |
I do not see anything wrong in your configuration, have you verified 'Preview' section to confirm running state is being returned by your vCenter? Also just a couple of differences when i compare it with my working setup.
Try the modifier rule, re-import and check if it helps. Also verify your custom variable 'vmstate' and its 'Data type' as 'string'. |
Hi, |
Hello,
I am having issues using a filter rule on an import from a vSphere host. We essentially only want to import machines in a "poweredOn" state.
The way I've set it up to get this data is as such:
With no filter it goes to import all of the VMs, as you would expect. With the filter rule set to poweredOn, none of them sync.
If I run the sync it shows in the sync data that the vars.vm_powerstate is set appropriately for on/off machines.
Is this an issue we're witnessing or some err in my configuration?
The text was updated successfully, but these errors were encountered: