azurerm_hdinsights_*_cluster: loosen work node count validation

[magodo]

The limitation should be loosened for work nodes (there already exists this case in the current code base), and I can't find the source for current hard limits.

From the document: https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-supported-node-configuration

If you need more than 32 worker nodes in a cluster, select a head node size with at least 8 cores and 14 GB of RAM.

And this is the exact behavior in Portal.

So I would suggest loosening the constraints for work node count.

(this fix #7342 )

[jackofallops]

Hi @magodo
Thanks for this PR, it looks mostly fine with one comment that I suspect is a copy-paste error? If you can address that I'll get the tests run and hopefully get this in the next release!

Thanks again
Ste

[magodo]

@jackofallops I have updated the typo, please take a look :)

[jackofallops]

Tests looking good:

(Failures are unrelated / transient)

[ghost]

This has been released in version 2.16.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.16.0"
}
# ... other configuration ...

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!