Azure / Azure/bicep-types-az

[Microsoft.App/containerApps]: ipSecurityRestrictions name showing up as mandatory

Open
#2,367 0 comments 0 reactions 0 assignees View on GitHub
inaccuracy
Dominant language
TypeScript
Stars
108
Forks
44
Avg merge
18h 53m
Merged PRs (30d)
29

Description

### Resource Type

Microsoft.App/containerApps

### Api Version

2024-03-01

### Issue Type

Other

### Other Notes

VSCode Bicep extension incorrectly shows the following warning when trying to define allowed IP ranges inside of properties/configuration/ipSecurityRestrictions
"The specified "object" declaration is missing the following required properties: "name". If this is a resource type definition inaccuracy, report it using https://aka.ms/bicep-type-issues.bicep[BCP035](https://aka.ms/bicep/core-diagnostics#BCP035)"

I think it's incorrect because giving a name to each rule is not required on the UI, so it shouldn't be in Bicep as well.

### Bicep Repro

ipSecurityRestrictions: [
{
action: 'Allow'
ipAddressRange: '173.245.48.0/20'
}
]

### Confirm

- [x] I have read the troubleshooting guide and looked for duplicates.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Microsoft.App/containerApps definition for API version 2024-03-01 and inspect the schema for properties/configuration/ipSecurityRestrictions. Reproduce the BCP035 warning with the provided Bicep snippet; done when omitting name no longer reports it as required.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.