-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation #158
Comments
Hey @KnKay, The Proxmox builder uses nested structs quite often (which also makes it difficult to generate the documentation automatically from the source files), so All in all, the documentation for EFI parameters looks correct to me. |
@sebastian-de - I'm going to undertake some documentation work on this. HCL is missing from a number of the key areas that made it hell for me to figure out. I'll update this issue with progress. I'm trying not to just rewrite the whole thing as I see fit, because it may not line up with what the expected standard is. On top of this, is there anything specific I should pay attention to? I'm going to be re-organizing a heap of it and changing some wordings here and there, and adding HCL examples, but is there any part of the flags that's currently missing? |
So, I spent a few hours fixing up the documentation to match my expectations and reordering things to match "Within each category, the available configuration keys are alphabetized". If someone would like to give the documents a quick review and let me know if I missed anything, that'd be great: I do still need to go through and sort out if I missed any properties, etc. but, for the moment, the documents should be a bit neater and have the various HCL vs JSON values. |
The doc for clone still appears to include elements from an ISO build ? |
Do you mind me asking which bits in particular? Judging based off the config.hcl2spec.go there are only 8 properties that ISO has that is unique, those being related directly to the ISO to use (iso_checksum, etc). Clone replaces these with 5 of it's own unique entries like "clone_vm_id" and "clone_vm". Otherwise, clone and ISO appear to share a number of attributes. Specifically, ISO makes use of:
Whereas Clone makes use of:
If you're referring to the contents of blocks like "addinitional_iso_files", I believe these have a consistent interface across the whole plugin, and so they shouldn't be difficult on a "clone vs ISO" basis. |
No I didn't get as far as examining all the individual properties, it was just on first glance I noticed that in the CLONE doc, the example starts with:
and then ...
Now I haven't done a Packer build with Proxmox for a while and it may only be convention rather than a strict syntactic requirement, but I have always used a a source of proxmox-clone if I'm doing a clone and proxmox-iso if I'm building from an ISO image. Otherwise it seems somewhat confusing if you mix the 2 regardless of whether it actually works or not, it just seems like a good practice IMHO. Something like this:
and for ISO builds:
But maybe YMMV HtHs Fraser |
Ah, good pickup. That was a case of my lazy ass copy-pasting from the ISO documentation I did first. Thank you for that. I've now fixed it so that it references Yes, it has to be the correct source for it to work properly, that's how it determines the plugin to load. My bad. |
Hi all,
saw there is some new efi stuff in the config.
https://github.com/hashicorp/packer-plugin-proxmox/blob/main/builder/proxmox/common/config.go#L107
due to the documentation
https://github.com/hashicorp/packer-plugin-proxmox/blob/main/docs/builders/iso.mdx?plain=1#L367
The variables are named differently. I guess this should be updated?
I have no proxmox to test at the moment. :(
The text was updated successfully, but these errors were encountered: