[BUG] APINames are not extracted

[jhuchler-iamds]

Release version

v6.0.1.4

Describe the bug

The API is displayed in the log (trace) but is not written to a file. Everything else is extracted correctly.

Strangely, it works with the following configuration, but i don't need extractAll.

JSON is displayed there.

Expected behavior

Extract API with apiNames: value

Actual behavior

Extract api with apiNames value not possible

Reproduction Steps

workspaceNames:
- ignore

apiNames:
- myAPIName

backendNames:
- myBackendName

diagnosticNames:
#- ignore

loggerNames:
#- ignore

namedValueNames:
#- ignore

productNames:
#- ignore

subscriptionNames:
- mySubscriptionName

tagNames:
#- ignore

policyFragmentNames:
#- ignore

versionSetNames:
#- ignore

Debug Trace ends like this:

info: extractor[0]
      Writing API operation policy file /home/vsts/work/1/artifacts-from-portal/sharedproducts/apim/apimArtifacts/apis/myAPIName/operations/post-action/policy.xml...
dbug: Microsoft.FeatureManagement.FeatureManager[0]

This configuration doesn't extract apiNames:

workspaceNames:
- ignore

apiNames:
- myAPIName

backendNames:
- myBackendName

diagnosticNames:
- ignore

loggerNames:
- ignore

namedValueNames:
- myNamedValues

productNames:
- rfmint

subscriptionNames:
- mySubscriptionName

tagNames:
- ignore

policyFragmentNames:
- ignore

versionSetNames:
- ignore

Debug Trace ends like this:

dbug: Microsoft.FeatureManagement.FeatureManager[0]
      The feature definition for the feature 'Workspaces' was not found.
info: extractor[0]

The write is simply missing here, although the API or the content for the

[github-actions]

  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.

[kimlood]

@jhuchler-iamds just found the same thing.
Removing the versionSetNames from the extractor config solves this issue or actually adding a valid version set to extract.
As a workaround for now..

[jhuchler-iamds]

I'm currently running release 6.0.2, but the issue still persists.
The configuration file located at https://github.com/Azure/apiops/blob/main/configuration.extractor.yaml

is approximately three years old. Is this file still considered current and aligned with the latest extractor behavior?
Additionally, does the versionSetNames property still exist in the current API Ops schema?

At the moment, the extractor only works if I comment out this setting entirely. However, I rely on the filtering capability provided by versionSetNames, and this functionality was still working correctly in version 5.0.1.