What is the keyword so extractor doesnt extract policy fragment and version sets?

Open
#688 6 comments 0 reactions 1 assignee View on GitHub

@guythetechie is already working on this.

Since Oct 17, 2024.

Assessment

This issue has not been assessed yet.

Description

Release version

6.0.1.3

Question Details

I have the below in configuration.extractor.yaml. However it is still extracting globalpolicy fragment and apiVersionSetsNames
Q1. What is the correct keyword to use so that it doesn't extract globalpolicy fragment and versionsets?
Q2. Can the documentation on wiki be updated to reflect all the supported resources and the correct keyword to use etc?

Image

Expected behavior

the extractor should skip over global policy fragments and apiversionsets

Actual behavior

the extractor is pulling down global policy fragments and apiversionsets

Reproduction Steps

use the attached configuration.extractor.yaml
apiNames:

  • test
    backendNames:
  • none
    diagnosticNames:
  • none
    loggerNames:
  • none
    namedValueNames:
  • none
    productNames:
  • none
    subscriptionNames:
  • none
    tagNames:
  • none
    policyFragmentNames:
  • none
    apiVersionSetsNames:
  • none
    groupNames:
  • none
Dominant language
C#
Stars
448
Forks
247
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 Azure/apiops

All issues in Azure/apiops

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.