[New Feature]: Validate all AppsAndFeaturesEntries fields #118948
Labels
Area-Validation-Pipeline
Issues related to the manifest validation pipeline.
Issue-Feature
Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Description of the new feature/enhancement
There is currently the label Manifest-AppsAndFeaturesVersion-Error which is applied when the version in AppsAndFeaturesEntries doesn't match the version that is written as the DisplayVersion. However, this doesn't seem to catch some other errors in AppsAndFeaturesEntries.
For example, in this PR, it didn't detect that the ProductCode was not valid for any of the ARP entries -
When AppsAndFeaturesEntries are specified in the manifest, the validation pipeline should check for an exact match of the complete entry, not just specific fields.
Proposed technical implementation details (optional)
When an AppsAndFeaturesEntries item is present in the manifest, validate that there is an exact match for the entire object. If a field is not specified in the manifest, allow any value. Note that each entry should be compared on all fields for an exact match, since some programs may create multiple entries which may match each individual field collectively
The text was updated successfully, but these errors were encountered: