You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Description
Currently no AzureRM provider version supports minExecutors and maxExecutors property when dynamicExecutorAllocation.
Currently AzAPI resource module can do it using below block , please add this feature in azurerm provider as well.
dynamicExecutorAllocation = {
enabled = bool
maxExecutors = int
minExecutors = int
}
Is there an existing issue for this?
Community Note
Description
Currently no AzureRM provider version supports minExecutors and maxExecutors property when dynamicExecutorAllocation.
Currently AzAPI resource module can do it using below block , please add this feature in azurerm provider as well.
dynamicExecutorAllocation = {
enabled = bool
maxExecutors = int
minExecutors = int
}
Reference https://docs.microsoft.com/en-us/azure/templates/microsoft.synapse/workspaces/bigdatapools?pivots=deployment-language-terraform#resource-format-2
New or Affected Resource(s)/Data Source(s)
azurerm_synapse_spark_pool
Potential Terraform Configuration
References
https://docs.microsoft.com/en-us/azure/templates/microsoft.synapse/workspaces/bigdatapools?pivots=deployment-language-terraform#resource-format-2
The text was updated successfully, but these errors were encountered: