When extracting just an api via the config.yaml file, the global policy xml file is extracted as well and shouldn't be.

[karlrissland]

Release version

v6.0.0-alpha.1.0.8

Describe the bug

My config.yaml is set to only extract an api as follows;

` apiNames:

• demo-conference-api

versionSetNames:

backendNames: [ignore]

diagnosticNames: [ignore]

loggerNames: [ignore]

namedValueNames: [ignore]

productNames: [ignore]

subscriptionNames: [ignore]

tagNames: [ignore]

policyFragmentNames: [ignore]

gatewayNames: [ignore]

groupNames: [ignore] `

Expected behavior

I expect only the API specification, the API apim config, the api policy, and the api operation policies to be extracted. In this use case, the developer should only be able to work with the api and it's specific policies.

Actual behavior

Unfortunately, the global policy is also extracted along with the api and it's policies.

Reproduction Steps

Setup an config.yaml file to extract just one api, run the extractor, not that the api and it's policies are extracted and the global policy is also extracted.