Azure / Azure/bicep

Add auto fix for use-protectedsettings-for-commandtoexecute-secrets

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

Description

@MarcusFelling What's the priority for adding fixes as opposed to just marking them?

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points and only asks about priority. First locate the existing use-protectedsettings-for-commandtoexecute-secrets rule and clarify the intended auto-fix behavior; done should include agreed scope and tests covering that behavior.

Written by the indexing model from the issue text.

Assessment

Domain
security, tooling
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.