clone_from_vm flag is quite misleading

[viktorbenei]

The description of the clone_from_vm flag right now:

Optional use a virtual machine instead of a template as the source for the cloning operation

From this description I'd think that when you want to clone from a virtual machine and not from a template you have to set clone_from_vm = true, but that doesn't seem to be the case. In vSphere 6 it seems that you can clone from templates and from virtual machines correctly regardless of what this clone_from_vm flag is set to.

Now, the misleading part: previously we did set this flag to true for our linked clones, as there we clone from virtual machines and not from templates. It works well in general, but clone_from_vm = true enabled some restrictions, for example the .compute_resource_name property is ignored (at least when you specify a cluster here) if clone_from_vm = true and the Cluster of the new VM will be the same as the original virtual machine's, regardless of what you set as compute_resource_name. If you use clone_from_vm = false even linked clones work correctly, and you can specify a different cluster for the linked clone, compute_resource_name is not ignored.

I have mainly two questions:

1. Is this a known bug/issue/thing?
2. Is this behavior intended? We're a bit worried that although this configuration (clone_from_vm = false with linked_clone = true) works right now, if this is not an intended behavior you might (rightfully) decide in the future to change this, which will break our configuration.

Thanks in advance, both for your response and for this awesome vagrant plugin! :)