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

Azure / apiops

APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.

MIT License

321 stars 189 forks source link

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?

Expected behavior

the extractor should skip over groups and apiversionsets

Actual behavior

the extractor is pulling down groups 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

Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.). Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

Azure / apiops