-
Notifications
You must be signed in to change notification settings - Fork 554
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
feat: Add 'import-from' parameter to qemu #606
Conversation
This feature should be used in the next version of the provider for sure! However, I feel that putting this in the resource properties would cause a lot of problem, this is not a parameter to be passed to the API every time we make a change(just an example). |
Ty. I agree with that assessment. For now, we're cloning from a template VM, but I would like to use this in the future. I might need some pointers on how to accomplish this... I have limited experience using this TF provider let alone developing a TF provider, so I'm kind of lost with how to only apply that parameter on initial creation. I'll poke around today a bit but I'm not sure how far I'll get. One other thing I noticed is that this might be an alternative to using iso or clone on the VM. When importing a disk image, neither parameter is needed. At the moment, one of those options is required, so I think this patch needs to add something to allow for a 3rd option instead of import/iso. |
I have a local development environment going. I found another issue that we'll run into, specifically that I want to use cloud-init without cloning from an existing template.
I'm going to modify the originally issue to include more details of my proposed use-case since this is turning into a bigger thing than just adding a parameter. That way, I'll have something to work from. |
1641542
to
590a361
Compare
Hi guys, can you tell me when will be the release of this feature? |
* fix(build): Detect KERNEL on MacOS * feat: Add 'import_disk' parameter to qemu --------- Co-authored-by: mleone87 <[email protected]>
@Tinyblargon this change didn't survive the transition to 3.x. Is it possible to add this back? Edit: I created #1236 for it. |
I think this addresses #605. It adds an optional
import-disk
parameter for VMs.I have no idea how to test this, or if I'm getting the additions made in the correct place. Please review with scrutiny and/or modify as-needed.