Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Synapse Spark pool module does not supports minExecutors and maxExecutors when dynamicExecutorAllocation is set to true. #18122

Open
1 task done
niks-singh opened this issue Aug 25, 2022 · 0 comments

Comments

@niks-singh
Copy link

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

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

dynamicExecutorAllocation {
    enabled = true
    minExecutors = 1
    maxExecutors = 3
  }

References

https://docs.microsoft.com/en-us/azure/templates/microsoft.synapse/workspaces/bigdatapools?pivots=deployment-language-terraform#resource-format-2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants