You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] v7 extractor groups exclusion no longer suppresses product-group artifacts under products #856
After upgrading from v6.0.1.10 to v7.x, excluding groups in the extractor configuration no longer suppresses product-group artifacts.
With v7, the extractor still produces product-group artifacts under product folders even when groups are excluded in the extractor config.
Expected behavior
When groups are excluded from extraction, product-group associations should also be excluded, or there should be a dedicated documented config option to suppress product-group child artifacts.
Actual behavior
With v7, the extractor still produces product-group artifacts under product folders even when groups are excluded in the extractor config.
Reproduction Steps
Use apiops v6.0.1.10 with extractor config excluding groups.
Run extractor against an APIM instance with products assigned to groups.
Observe that product-group artifacts are not extracted.
Upgrade to v7.x.
Use the equivalent v7 extractor config excluding groups.
Run extractor against the same APIM instance.
Observe that product-group artifacts are still extracted under products.
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.
Activity
github-actions commentedon May 19, 2026
guythetechie commentedon May 20, 2026
nithinjamespallicka - thanks for the well-described issue. Investigating.