Add support for Rule Exclusions for the Template Analyzer

Open
#77 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the Template Analyzer configuration items in the linked Security DevOps wiki and the Template Analyzer documentation on customizing evaluation outputs. Determine how this extension currently passes configuration to the analyzer; the work is done when users can provide rule exclusions or a configuration file and excluded rules no longer fail the pipeline.

Written by the indexing model from the issue text.

Description

Issue

Currently the configuration items for the Template Analyzer through this app are defined here.

There is no way to add rule exclusions. This is useful in the case where some of the rules might not apply and we don't want them to fail the pipeline.

On the Template Analyzer application directly it does have support for rule exclusions via a configuration file as documented here.

Suggestion

Include a way to define rule exclusions that can be passed to the template analyzer app. Alternatively provide a way to provide a configuration file to the app (this will make the tool much more flexible).

Dominant language
TypeScript
Stars
86
Forks
22
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/security-devops-azdevops

All issues in microsoft/security-devops-azdevops

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.