Azure / Azure/bicep

Linter rule to suggest against targetScope = tenant

Open
#3,016 7 comments 0 reactions 0 assignees View on GitHub
devdiv enhancement story: linter rules
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

It seems there's not really any practical reason to use `targetScope='tenant'`, as tenant-scoped resources can be deployed from Bicep files at other scopes. Also, `targetScope = 'tenant'` requires tenant-level permissions, which very few users have.

This seems like a good candidate for a linter rule, maybe to point customers to a doc explaining this and why they should avoid it?

Contributor guide

Open the contributing guide

Research direction

Start by locating the linter-rule entry points and documentation associated with the Bicep targetScope declaration. Confirm how tenant-scoped resources can be deployed from other scopes and define the expected warning and documentation link for targetScope='tenant'. Done means the rule and its guidance clearly discourage unnecessary tenant-scope usage.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.