[BUG] Extractor is trying to read whole APIM instance when specific config provided - regression of bug #610 #830
Description
Release version
v7.0.0-beta.1.0.0
Describe the bug
I am specifying selected artifacts to extract. my configuration extractor below
apis: []
versionSets: []
workspaces: []
backends: []
namedValues: []
products: []
subscriptions: []
tags: []
policyFragments:
- fragment1
- fragment2
groups: []
loggers: []
diagnostics: []
gateways: []
When extractor runs, it reads all the APIM artifacts, tags,backends,products,subscriptions,fragments - everything from APIM instance. Once everything is read, then it extracts just the artifacts specified. In my case fragment1,2
But it reads the whole APIM instance.
In log, I can see extractor is using the extractor config.
CONFIGURATION_YAML_PATH ................... /home/runner/work/_temp/configuration-extractor.yaml
When you enable the LOG_LEVEL Trace on extractor you can see that it is iterating over everything on APIM instance and then skipping the artifacts not specified.
If LOG_LEVEL is not Trace then you get only the concise view which makes it look like it is not iterating over everything.
So pls enable LOG_LEVEL Trace to reproduce the problem
I have attached the log file from GHA.
Search for "Skipping" in log file where you can see extractor skipping. However you can also see extractor iterating over all artifacts on APIM.
Expected behavior
extractor should only read the artifacts specified in extractor config and not the entire APIM instance.
This is a major issue when APIM have 100s of artifacts and extractor is unnecessarily reading everything when it just have to extract 1 artifact
Actual behavior
extractor reads all resources/artifacts from APIM instance
Reproduction Steps
set version to v7.0.0-beta.1.0.0
extractor config
apis: []
versionSets: []
workspaces: []
backends: []
namedValues: []
products: []
subscriptions: []
tags: []
policyFragments:
- fragment1
- fragment2
groups: []
loggers: []
diagnostics: []
gateways: []