[FEATURE REQ] Flag to disable extract of global policy
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
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.
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.
- Dominant language
- C#
- Stars
- 448
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/apiops
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·
-
Issue-Enhancement Needs-Triage
Difficulty 1/5 Under an hour Newbie friendliness 86/100
PowerShell/PowerShell#28061 · 2 reactions ·
-
dependencies needs-team-triage server-Azure.Mcp
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
aspnet-core/svc aspnetcore-signalr/subsvc doc-enhancement Pri2 SignalR
Difficulty 1/5 Under an hour Newbie friendliness 88/100
dotnet/AspNetCore.Docs#37729 ·