…f the same component processing the same messages, resulting in a lot of data update conflicts
Brief description of the PR.
In a previous PR a random component in event bus clients id was introduced in order to allow multiple components (e.g.: lifecycle, telemetry, etc) to consume the same event.
Multiple instances of the same component, however, should not process the same event multiple times, as this would result in potential update conflicts on affected entities.
As the event module name (unique for each component) was already previously introduces, this PR removes the unnecessary random component which was added at configuration time.
…f the same component processing the same messages, resulting in a lot of data update conflicts
Brief description of the PR. In a previous PR a random component in event bus clients id was introduced in order to allow multiple components (e.g.: lifecycle, telemetry, etc) to consume the same event. Multiple instances of the same component, however, should not process the same event multiple times, as this would result in potential update conflicts on affected entities. As the event module name (unique for each component) was already previously introduces, this PR removes the unnecessary random component which was added at configuration time.