Bicep module to support debugSetting feature
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
UPDATE: the issue is now only for debugSetting, not complete parity with `Microsoft.Resources/deployments`
I was helping on an issue yesterday and wanted to turn on `debugSetting` on a nested deployment (I was using a module) and it hit me.
It is very easy and convenient today to use modules, they translate into `Microsoft.Resources/deployments`. There is no way to set the properties on a Module like it is possible to with `Microsoft.Resources/deployments`
**Describe the solution you'd like**
I'd like to be able to control the properties like
```
debugSetting: {
detailLevel: 'string'
}
```
I know I could declare a deployment resource in Bicep but I loose the transpile and ease that module provides.
I'd like to be able to declare the following in a module:
```
module keyVault 'keyvault.bicep' = {
name: 'keyVaultDeployment'
properties: {
debugSetting: {
detailLevel : 'requestContent, responseContent'
}
}
}
```
Contributor guide
Research direction
Start by locating how Bicep module properties are represented and translated to Microsoft.Resources/deployments. Trace the handling of the module declaration shown in the issue and identify the existing tests for deployment or module properties. Done means a module can accept debugSetting.detailLevel and emits the corresponding deployment property.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100