Azure / Azure/bicep-registry-modules
[AVM Module Issue]: Data-Factory linked-service AzureDatabricks typeProperty newClusterNumOfWorker
- Dominant language
- Bicep
- Stars
- 736
- Forks
- 564
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 30
Description
### Check for previous/existing GitHub issues
- [x] I have checked for previous/existing GitHub issues
### Issue Type?
Bug
### Module Name
avm/res/data-factory/factory
### (Optional) Module Version
0.11
### Description
When deploying an Azure Data Factory Linked Service for Azure Databricks using the Bicep Verified Module, the newClusterNumOfWorker property does not correctly translate autoscaling values. According to Microsoft’s documentation, this property should accept a string-formatted Int32 such as:
"1" → fixed number of workers
"1:10" → autoscale between 1 and 10 workers
However, when specifying a range (e.g., "1:10"), the module does not configure autoscaling. Instead, it only applies a fixed number of workers.
Expected Behavior
Providing a value like "1:10" should configure the Databricks job cluster to autoscale between 1 and 10 workers.
Actual Behavior
The module ignores the autoscale range and applies only a fixed worker count.
Reference
Microsoft documentation for AzureDatabricksLinkedServiceTypeProperties.newClusterNumOfWorker:
https://learn.microsoft.com/en-us/azure/templates/microsoft.datafactory/factories/linkedservices?pivots=deployment-language-bicep
### (Optional) Correlation Id
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.