Any ideas out there?
The solution I can think of for this situation is to use compliance job with the all the configuration file entries as parts and adding the single entry as and ignored path to the component exception. In that way the component should be compliant with and without the specific config entry but will be not compliant for any other entry which is not in the list.
you don't need the exception - you can handle excluding the differing entry in the rule condition. w/ an audit i think you could add each config file entry to the template - that would compare only those entries i believe.
Compliance jobs wouldn't work, since I need to compare a group of servers against a "master" in the group. Since these servers could change with application updates, it would require updating the compliance rules too often. In addition I would need to create a separate one for each additional group of servers, rather than reusing the component template across many groups.
And adding the individual configuration entries won't work, as additional entries found in the target would not be listed.
As an example, for our Sun Webservers, I need to compare server.xml to ensure they are configured the same, disregarding the following section:
If I added all the other entries individually, I would have not found that one server had an additional configuration entry of:
Opened a case with support to find this just isn't possible, but there are existing enhancement request for this.