Support for azurerm_orchestrated_virtual_machine_scale_set documentation adjustment

[alselivonets]

Is there an existing issue for this?

• I have searched the existing issues

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 "me too" comments, 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 and review the contribution guide to help.

Description

In documentation for azurerm_orchestrated_virtual_machine_scale_set in argument reference block there's a misleading description of eviction_policy. It says:
"eviction_policy - (Optional) The Policy which should be used Virtual Machines are Evicted from the Scale Set. Possible values are Deallocate and Delete. Changing this forces a new resource to be created."

The Microsoft documentation says that eviction policy can be set only for Spot VMs. The description for eviction_policy argument should say:
"eviction_policy - (Optional) The Policy which should be used by Spot Virtual Machines that are Evicted from the Scale Set. Possible values are Deallocate and Delete. Changing this forces a new resource to be created."

See reference documentation below.

New or Affected Resource(s)/Data Source(s)

azurerm_orchestrated_virtual_machine_scale_set

Potential Terraform Configuration

No response

References

https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/orchestrated_virtual_machine_scale_set
https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/use-spot
https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.management.compute.models.virtualmachine.evictionpolicy

[alselivonets]

Hi, @rcskosir. Could you please review above Pull Request?

[github-actions]

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.