-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
azurerm_hdinsights_*_cluster: loosen work node count validation #7430
azurerm_hdinsights_*_cluster: loosen work node count validation #7430
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
azurerm/internal/services/hdinsight/hdinsight_hadoop_cluster_resource.go
Outdated
Show resolved
Hide resolved
@jackofallops I have updated the typo, please take a look :) |
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 ... |
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 👉 [email protected]. Thanks! |
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
And this is the exact behavior in Portal.
So I would suggest loosening the constraints for work node count.
(this fix #7342 )