Tool behavior when OriginOfCondition property in a LogEntry points to a collection

[luke-terry-vertiv]

I think the tool should not report an error when the OriginOfCondition in a LogEntry points to a collection when the log was created when an attempt to create or delete a collection member failed -- examples include failing to create a certificate resource, session resource, user account, etc.

Maybe an exception list can be checked against for messages that are expected to happen in those cases? Also, it would be good to have a solution for OEM registries which would not be included in any exception list provided by the tool

[mraineri]

By definition today, OriginOfCondition is not allowed to point to resource collections.

OriginOfCondition points to the type "Resource.Item", which allows for either resources or referenceable members.

[luke-terry-vertiv]

Yeah, understood about the current definition and the schema guidance saying it should not point to collections. What would an expected OriginOfCondition be in those cases, then? It seems a bit counterintuitive to me for the OriginOfCondition to be something other than the collection URI specified in the request