Michael Kuzmin

This sounds dangerous, but I cannot reproduce yet. Can you post a minimal example?

CPU_limit issue also reported in #119. fixed in https://github.com/jetbrains-infra/packer-builder-vsphere/releases/tag/v2.0.1

Do you actually use tags in vSphere? they do exist but require additional permissions.

I want to hear a real use case first. Are you already using tags outside of Packer? What kind of values do they contain?

My point is tags in vSphere is not what you usually expect from such a feature. They require to be an administrator of the whole vCenter. That’s why I’m asking...

`configuration_parameters` are already supported. For notes please file a separate issue. Also, this would be a very simple PR like #46.

I see two problems here: - `boot_command` requires ESXi 6.5, and cannot be executed on older hosts due to lack of API. - DRS-enabled clusters are configured without `host` parameter...

yes, that's a bug - we need to escape the string. I solve this issue by using `{{timestamp}}`

@agowa338 > This would allow us to have 4 cores and 16gb of ram while building the image, but not in the final template. Don't you find such low-level customization...

@segator > I need to set disk.EnableUUID Can it be done at VM creation?