provider/vsphere: Setting to skip customization #6355
Conversation
| if err != nil { | ||
| return err | ||
| if vm.skipCustomization { | ||
| log.Printf("[DEBUG]VM customization skipped") |
There was a problem hiding this comment.
This is missing a space between [DEBUG] and the actual message.
|
Hi @thetuxkeeper! This looks good - I've left a few minor nitpicks on the code. Once addressing these, could you squash your commits, and rebase onto master - and we can get this merged in time for the next release. Thanks for your work! |
|
Hi @jen20 |
|
Thanks @thetuxkeeper! This is merged into master and will appear in the 0.6.16 release. |
|
Thanks for reviewing and merging! |
|
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. |
ghost
locked and limited conversation to collaborators
We ran into the problem like described in #3562.
We use a template with empty disks. After deploying it will boot with PXE into CoreOS. The CoreOS will load an install cloud-init and install to disk. After a reboot it is ready for ansible.
Since "other Linux ..." is not supported for customization, terraform failed and I found no setting to change it.
With this new setting (skip_customization) you are able to skip the customization part.