Azure / Azure/apiops

[FEATURE REQ] Flag to disable extract of global policy

Open
#720 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
448
Forks
247
PR merge metrics
No merged PRs in 30d

Description

### Please describe the feature.

The ApiOps documentation describes a model for supporting distributed API teams working with a single API Management set of resources. The approach describes each team having a dedicated repository and using the Extractor configuration file to control which APIM resources are extracted.

One challenge with this approach is that with the current implementation of the Extractor, each team would end up extracting APIM's global policy. This means teams could potentially introduce global policy changes that introduces issues for other teams using the same APIM. Ideally, customers should have the ability to disable extracting global policy. This would ensure each independent API team doesn't need to extract global policy and customers could have a central team that manages global policy through a separate repo.

Contributor guide

Open the contributing guide

Research direction

Start by locating the Extractor implementation and the configuration file described in the issue, then trace how global policy is selected for extraction. Check whether existing extraction tests cover global policy and identify where a disable option would be validated. Done means teams can disable global policy extraction while other APIM resources continue to be extracted.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
api, devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 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.