Skip to content
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

vsphere_ha_vm_override : missing disable state for ha_vm_restart_priority #1493

Closed
doumhfr opened this issue Oct 13, 2021 · 1 comment · Fixed by #1505
Closed

vsphere_ha_vm_override : missing disable state for ha_vm_restart_priority #1493

doumhfr opened this issue Oct 13, 2021 · 1 comment · Fixed by #1505
Labels
enhancement Type: Enhancement

Comments

@doumhfr
Copy link

doumhfr commented Oct 13, 2021

Description

On vsphere GUI, when we set a vm override for vm restart priority, we can choose : highest, high, normal, low, lowest and disable

but the vsphere_ha_vm_override only support :
ha_vm_restart_priority - (Optional) The restart priority for the virtual machine when vSphere detects a host failure. Can be one of clusterRestartPriority, lowest, low, medium, high, or highest. Default: clusterRestartPriority.

no disable value

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@doumhfr doumhfr added the enhancement Type: Enhancement label Oct 13, 2021
appilon pushed a commit that referenced this issue Jan 28, 2022
Addresses #1493
- Adds `disabled` to `vsphere_ha_vm_overide`.
- Updates `vsphere_ha_vm_overide`resource docs to include `disabled`.
- Updates `vsphere_ha_vm_overide`resource docs to vSphere 7.0 reference.

Signed-off-by: Ryan Johnson <johnsonryan@vmware.com>
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Type: Enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant