[BUG] All namedValues are being extracted when using namedValues: [] in configuration.extractor.yaml instead of none being extracted.

[JProvAnt]

Release version

7.0.0-alpha.2.0.0

Describe the bug

Empty configuration in extractor
Previously, if we wanted to skip extracting all resources of a type, we had to put a random placeholder value (e.g. ignore). We now support the more intuitive [].

This seems to not be working for namedValues, in my tests ALL named values are being extracted when using the new [] placeholder and section names

Below is configuration.extractor.yaml:

apis:
  - containerAppDummy

backends: 
  - containerappdummyBackend

diagnostics: []

loggers: []

namedValues: []

products:
  - containerappdummy

subscriptions:
  - containerappdummy

tags: []

policyFragments: []

groups: []

Even though namedValues has an empty [] like the other properties, ALL Named Values are being extracted as can be seen in the pipeline screenshot below:

The other properties like tags and diagnostics are in contrast being correctly ignored by the extractor:

Expected behavior

If configuration.extractor.yaml has namedValues: [] then NO Named Values should be extracted.

Actual behavior

When configuration.extractor.yaml has namedValues: [], ALL Named Values are being extracted.

Reproduction Steps

• In configuration.extractor.yaml add namedValues: []
• Run pipeline
• All Named Values are extracted instead of none.

[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.

[megamax34]

@JamesProant
In the documentation they specify this case.
"A apiNames section which includes a bogus name (e.g. ignore) in configuration (apiNames:[ignore]) means no apis will be extracted. The reason we did not use an empty array instead to indicate ignoring an artifact has to do with the fact that an empty array doesn’t work here is because of the way YAML configurations work with .NET configuration. Passing a field with an empty array is essentially the same not passing that field at all."

Use namedValues: [ignore]

[JProvAnt]

Maxmilian Pawlikowski (@megamax34) please re-read the first paragraph of this issue. I included a link there to the change in version v7.0.0-alpha.1.0.1 where using ignore changed to an empty [].

[megamax34]

Ah I see that this is supposed to be improved in v7, my bad I missed that. Just for curiosity, does it work if you use [ignore]?

[guythetechie]

James (@JProvAnt) - we changed the configuration keys in v7.

• v6: camel case (e.g namedValues).
• v7alpha2: space-separated (e.g. named values).
• v7alpha3+: snake case (e.g. named_values).

Sorry, we did a poor job documenting this. I'm about to release v7alpha3, and this should be documented in its release notes. Please feel free to reopen the issue if you still encounter issues.

[JProvAnt]

guythetechie Thanks. A few clarifying questions:

• Are all configuration keys changed to use snake case in v7alpha3? Including sub-configuration keys like the displayName of the namedValues in the configuration.dev.yaml file should now be display_name?
• Is policyFragments now policy_fragments in configuration.extractor.yaml?
• Is apimServiceName now apim_service in configuration.dev.yaml?
• Is serviceUrl now service_url?

Can you please document this more thoroughly?

[guythetechie]

James (@JProvAnt) - we've reverted back to camelCase in our latest beta release. The configuration sample files in the v7 branch should be accurate.