You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implemented in development (#589), in the image ghcr.io/bb-ricardo/netbox-sync:development. Two filters: vm_exclude_by_resource_pool_filter and vm_include_by_resource_pool_filter, regexes like vm_exclude_filter. They are matched against the resource pool path (Parent/Child, root pool left out) and against the plain pool name; a VM is skipped when either matches the exclude filter, and kept by the include filter when either matches. A VM in the root pool is judged by the name Resources.
Could you try it against your vCenter? Run with -n first, then a real run and a second one (the second should change nothing in NetBox), and say what came out, here or in the call for testing: #592. Nothing changes unless the option is set, so pulling the image is safe. It goes into 1.10.0, the next feature release.
Activity
bb-Ricardo commentedon Mar 9, 2026
Hi, this is currently not possible. There is no detection of resource pool implemented.
semx commentedon Oct 10, 2026
Implemented in
development(#589), in the imageghcr.io/bb-ricardo/netbox-sync:development. Two filters:vm_exclude_by_resource_pool_filterandvm_include_by_resource_pool_filter, regexes likevm_exclude_filter. They are matched against the resource pool path (Parent/Child, root pool left out) and against the plain pool name; a VM is skipped when either matches the exclude filter, and kept by the include filter when either matches. A VM in the root pool is judged by the nameResources.Could you try it against your vCenter? Run with
-nfirst, then a real run and a second one (the second should change nothing in NetBox), and say what came out, here or in the call for testing: #592. Nothing changes unless the option is set, so pulling the image is safe. It goes into 1.10.0, the next feature release.