[BUG]

Start with the extractor pipeline using configurator.extractor.yaml and reproduce the run for dealer-api-uat with the listed subscriptionNames. Compare the generated output when extracting the specific API with an all-resource extraction, including the extra artifact-name/version sets folder and global policy XML. Done means the requested subscriptions and global policy are extracted without the unwanted folder.

Release version

APIOps Toolkit for Azure APIM v5.1.4

Describe the bug

Hi,

I am Rhenatas Rajan from Toyota Motor Corporation Australia.

We have a plan to implement APIOPS in our environment. Based on that i downloaded the v5.1.4 code and started implementing.
During implementation, I found the following issues. I reached out to Microsoft support program. They directed me to this forum.

Following are the issue I am facing :

1. While extracting the specific api using configuration.extractor.yaml file, i am getting and additional folder named artifact-name/version sets. This is not required.
2. I need to extract the specific subscription names that is associated to the API. But, it does not extract when i try to extract specific API. Whereas, subscriptions gets populated when i extract all.
3. I would like to extract only the Global policy xml . But, that is not happening.

Please do the needful.

apiNames:

• dealer-api-uat

productNames:

• general-services
• vehicle-import-service

tagNames:

subscriptionNames:

• Continuous-Integration-subscription
• Vehicle-Import-Service-subscription

backendNames:

diagnosticNames:

loggerNames:

namedValueNames:

policyFragmentNames:

Expected behavior

subscription folder should appear

• Continuous-Integration-subscription
• Vehicle-Import-Service-subscription

Actual behavior

Subscription folder not appearing

Reproduction Steps

1. Run the extractor pipeline with extract using configurator.extractor.yaml pipeline with the below mentioned entries:

apiNames:

• dealer-api-uat

productNames:

• general-services
• vehicle-import-service

tagNames:

subscriptionNames:

• Continuous-Integration-subscription
• Vehicle-Import-Service-subscription

backendNames:

diagnosticNames:

loggerNames:

namedValueNames:

policyFragmentNames: