fix: add memory_reservation_locked_to_max
property to r/vsphere_virtual_macine
schema for sr-iov
#2093
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The
memory_reservation_locked_to_max
property was missing fromvsphere_virtual_macine
schema (both data and resource). The property of the VM was automatically set tofalse
ifmemory
andmemory_reservation
properties have different values.With this commit the property can be set to true explicitly and it will be applied only if
memory
andmemory_reservation properties
have same values. If thememory_reservation_locked_to_max
is not explicitly set totrue
the original behaviour is preserved.Acceptance tests
Output from acceptance testing:
Release Note
Release note for CHANGELOG:
References
Closes #2091