Azure / Azure/bicep

Support for "justUseNext" function

Open
#591 2 comments 0 reactions 0 assignees View on GitHub
enhancement provider improvement
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 2h
Merged PRs (30d)
79

Description

**Is your feature request related to a problem? Please describe.**
Currently need to use PowerShell to get next available priority for NSG, Firewall etc rules and then inject this value into ARM template for deployment.

**Describe the solution you'd like**
Similar to [440](https://github.com/Azure/bicep/issues/440) - would be nice to have a bicep function to get next available priority, free IP in a range etc:

```
resource nsg 'Microsoft.Network/networkSecurityGroups@2016-09-01' = {
name: networkSecurityGroupName
location: location
properties: {
securityRules: [
{
name: 'default-allow-rdp'
properties: {
priority: 1000 <----- This can be a Bicep function
sourceAddressPrefix: '*'
protocol: 'Tcp'
destinationPortRange: '3389'
access: 'Allow'
direction: 'Inbound'
sourcePortRange: '*'
destinationAddressPrefix: '*'
}
}
]
}
}
```

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the linked issue 440 and the example NSG security rule in this issue. Clarify whether the request is limited to next available priorities or also covers free IPs and other ranges; done requires an agreed function design and behavior before implementation can be scoped.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, powershell
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.