-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the keyword so extractor doesnt extract policy fragment and version sets? #688
Comments
|
@waelkdouh I think this is a bug than a new feature. The documentation says it should be possible to exclude globalpolicyfragments and version sets, however it is not excluding it. |
@martin2176 - looking at the code, I don't see a filter for global policy. Can you point to the documentation where it says you can filter out global policy? As for version sets, it should be |
@guythetechie |
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 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:
backendNames:
diagnosticNames:
loggerNames:
namedValueNames:
productNames:
subscriptionNames:
tagNames:
policyFragmentNames:
apiVersionSetsNames:
groupNames:
The text was updated successfully, but these errors were encountered: