azurerm_virtual_desktop_scaling_plan - Mixed/wrong argument description

[teemukj]

trafficstars

Is there an existing issue for this?

• [X] I have searched the existing issues

Community Note

• Please vote on this issue by adding a :thumbsup: 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

Terraform Version

1.2.9

AzureRM Provider Version

3.23.0

Affected Resource(s)/Data Source(s)

azurerm_virtual_desktop_scaling_plan

Terraform Configuration Files

https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/virtual_desktop_scaling_plan

Debug Output/Panic Output

In the documentation of "virtual_desktop_scaling_plan" resource, two argument descriptions are wrong, as they should be swapped in place.

Expected Behaviour

ramp_up_capacity_threshold_percent attribute should be described as the threshold value for the autoscaling process during the ramp-up phase.

ramp_up_minimum_hosts_percent attribute should be described as the minimum percentage of session hosts to be available during ramp-up/peak.

Actual Behaviour

Currently the descriptions of these attributes are mixed/swapped in the azurerm documentation.

Steps to Reproduce

No response

Important Factoids

No response

References

https://learn.microsoft.com/en-us/azure/virtual-desktop/autoscale-scenarios

[sinbai]

Hi @teemukj thanks for bringing this to our attention. PR has been submitted to fix it.

[github-actions[bot]]

This functionality has been released in v3.24.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions[bot]]

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.