Bicep build does not block file with 800+ resources
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
**Bicep version**
Using `Azure/bicep-build-action@v1.0.0` GitHub Action.
**Describe the bug**
Bicep build does not block file with 800+ resources in it
**To Reproduce**
Steps to reproduce the behavior:
1. Create template with more than 800 resources.
```
param resourceNamePrefix string = 'promitor-scale-resources-'
resource workflowInNorthEurope 'Microsoft.Logic/workflows@2019-05-01' = [for i in range(1, 801): {
name: '${resourceNamePrefix}-workflow-ne-${format('{0:D3}', i)}'
location: 'northeurope'
tags: {
region: 'Europe'
app: 'promitor-large-scale-testing'
instance: '${resourceNamePrefix}-workflow-we-${format('{0:D3}', i)}'
}
properties: {
state: 'Enabled'
definition: {
'$schema': 'https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#'
contentVersion: '1.0.0.0'
parameters: {}
triggers: {}
actions: {}
outputs: {}
}
parameters: {}
}
}]
```
2. Deploy
**Additional context**
Deploy fails though.
Contributor guide
Research direction
Start by reproducing the 800-resource template with Azure/bicep-build-action@v1.0.0 and compare the build result with the deployment failure. Determine which stage should reject the template and document the expected threshold behavior; done means the reported case is consistently handled as intended and covered by an appropriate regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github-actions
- Domain
- build-system, ci-cd, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100