In our case, we have two pools (Test & Production). XO allows you to create or import a template with the same name into each pool. This is reasonable.

When deploying a VM with tofu, first we configure the pool we are using with xenorchestra_pool. But when we configure xenorchestra_vm and select the template by name, tofu fails because it sees both templates with the same name - and ignores the fact that they are in different pools.

found `2` templates with query {Id: Uuid: Boot:{Firmware: Order:} NameLabel:<my_template_name> PoolId: TemplateInfo:{Arch: Disks:[]} VBDs:[]}. Templates must be uniquely named to use this data source

The templates ARE uniquely named, within their pool, as permitted by XO. Would it be possible please for the tofu VM resource to search for the template in the pool that has been configured?

Many thanks,
Graham