-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
provider/vsphere: Add support for memory reservation #6036
provider/vsphere: Add support for memory reservation #6036
Conversation
Hi @tkak this PR looks good - please can you rebase it against master so we can get this merged? Paul |
This PR needs rebased so that we can merge it I asked @tkak just yesterday Paul |
@stack72 thanks missed that :) |
Hi @tkak and @chrislovecnm - I've just looked over this now - even if the conflicts are resolved during merge there is a problem with the vendored version of the SDK for vSphere that is preventing compilation. |
38300a7
to
6ebfcce
Compare
Thank you @stack72, @chrislovecnm and @jen20. I fixed my PR. |
@jen20 much thanks for the help! How are we looking on the merge now? |
"memory_reservation": &schema.Schema{ | ||
Type: schema.TypeInt, | ||
Optional: true, | ||
ForceNew: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you really want to force a new resource when memory_reservation changes? Can it not be changed once created?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It can change on existing VMs with VMware vSphere. But it needs to be set ForceNew option because there is no support to update resources now.
@tkak (@chrislovecnm) - 2 small nit picks that could potentially be taken care of post-merge. Well 1 nit pick and 1 question I guess |
@stack72 please nit pick away ... We want good code ... lol |
6ebfcce
to
cba1567
Compare
Hi @tkak Thanks for the updates here. I understand now why the Update func hasn't been added to the schema for the @chrislovecnm it may be worth adding that to the overall tracking for the issues for vsphere provider :) Thanks all for the work here - this looks good to merge :) P. |
@stack72 sorry please more info |
@chrislovecnm currently, this vm resource only supports Create, Read and Delete. There are no update operations included, therefore if someone changes a value it will not get updated, it will create a new resource So the large list of enhancements that were being tracked may want to have this included on it - to support the appropriate update operations Make sense? |
@stack72 thanks and appreciate the merge |
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. |
This PR adds memory reservation support for
vsphere_virtual_machine
resource. I'd like to submit again, #4138.