oem-integrator - Filter schema files in the output dir based on supported schema/versions

[ryweldon]

Requesting enhancement that provides a method to limit the schema files produced in the output directory.

• Provide a method to completely remove schema that are unsupported
  -- Consider using the /uris property if all are "@meta.Enabled": false

• Provide a method to limit schema versions for a given schema based on the supported versions
  -- Consider pulling in the /definitions/{schema}/anyOf array from the base entity into the associated config file and use the @meta.Enabled property to indicate support.

Goal is to use the output schema as direct input into the doc-generator without performing any post-processing.

[mraineri]

This would be a good addition. We might want to control with with a config option though (I have folks expecting all versions of the file.... for some reason). Will work with @abhirupseal to see what he thinks.

[jautor]

At least for the "global" removal, supporting a @meta.Enabled option at the schema level in the configuration file would be easy to understand.

And I agree this is an important feature to add, as it allows use of a clone of Redfish-Publications as the source folder without modification.

[abhirupseal]

I have a fix for the first issue which I will be pushing soon. However, I'm not too sure of the second one. It could become quite tedious to do this via a config as the versions keep changing every release. I feel it would be better for the service implementer to have some separate scripts to do this.