SanjayVas
commented
4 weeks ago Note that no two registered EventGroup metadata descriptors can share types unless those types are in the "known event group metadata type" set. This is controlled by the --known-event-group-metadata-type option passed to the Kingdom and Reporting systems. See the v0.5.2 release notes for more details.
Background
The primary intent of the EDP simulator is to facilitate Halo integration tests. It is however also useful for operators of Halo systems to use it for their own testing, so some functionality has been added to support this. The EDP simulator currently uses specific EventGroup metadata descriptors to control requisition fulfillment behavior w.r.t. how events are generated. The intent was that real EDPs could also be made to implement the same behavior to support conformance testing. With the advent of efforts such as HMSS, EDP libraries, and the EDP aggregator, the need for this kind of performance testing has diminished. Separately, Halo operators have indicated a desire to use the EDP simulator for end-to-end testing of other parts of their systems such as EventGroup search.
Proposal
Allow operators to specify EventGroup metadata using any EventGroup metadata descriptor. This means that the metadata descriptor cannot be used to control event generation behavior. Instead, this behavior is solely controlled via configuration of the simulator itself.