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
Therefore I suggest to issue a warning with packer validate, when proxmox is used instead of proxmox-iso.
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Currently Packer includes the plugin alias
proxmox
:packer/command/vendored_plugins.go
Line 120 in 512ef1a
The alias was added for backwards compatibility when the plugin was split into
proxmox-iso
andproxmox-clone
: a140c13This works fine until a user that has
proxmox
in their template wants to use a specific version of the plugin, using apacker
block.In this case the internal plugin is used instead of the one specified in the
packer
block:See the example template and full log below.
This behavior is quite confusing and there are a number of reported issues because of that (and possibly more):
Therefore I suggest to issue a warning with
packer validate
, whenproxmox
is used instead ofproxmox-iso
.Community Note
Simplified Packer Template
Log Fragments and crash.log files
The text was updated successfully, but these errors were encountered: