Azure / Azure/bicep

Resource Derived Types -> Add support for User Defined Types in referenced modules

Open
#13,677 6 comments 2 reactions 0 assignees View on GitHub
enhancement
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

**Is your feature request related to a problem? Please describe.**
When you declare a user defined type as a parameter of a module, you now cannot reference this type dynamically.

```
param myUDTValue string
param myUDTValue2 int

module myModule 'br/recipe:api:v1.0.4' = {
name: 'myModule-${deploymentDate}'
scope: resourceGroup
params: {
location: location
myUDT: {
value: myUDTValue
secondValue: myUDTValue2
}
}
}
```

**Describe the solution you'd like**
A way to reference myUDT so we can provide the values via bicepparam, like:

```
param myUDTParam resource

module myModule 'br/recipe:api:v1.0.4' = {
name: 'myModule-${deploymentDate}'
scope: resourceGroup
params: {
location: location
myUDT: myUDTParam
}
}
```

Contributor guide

Open the contributing guide

Research direction

Start with the issue's examples of user-defined types in referenced modules and bicepparam files, then trace how module parameter types are resolved. Done means a user-defined type from a referenced module can be declared as a parameter and supplied through bicepparam as shown.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.