Azure / Azure/bicep

Extend custom linter configuration to cover BCP081 Resource type does not have types available

Open
#5,286 2 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.**
There are often cases where specific resource providers api versions can be used but aren't in the bicep intellisense/linter. Whilst the "best" case would be for 100% accuracy here, I think suppressing the warning through a custom bicepconfig.json is also viable.

**Describe the solution you'd like**
Simple solution;
A new rule to be useable in bicepconfig.json

"resource-types": {
"level": "Info"
}

Better solution
To be able to specifically add resource apis to ignore.

"resource-types": {
"level": "Off",
"ignoredRPs": [
"Microsoft.Authorization/roleAssignments@2021-04-01-preview"
]
}

Contributor guide

Open the contributing guide

Research direction

Begin with the BCP081 linter rule and the bicepconfig.json settings shown in the issue. Review existing custom linter configuration behavior, then determine whether the completed change supports only a configurable severity or also ignored resource API entries, with tests covering the chosen configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.