[midPoint-git] [Evolveum/midpoint] 2c94f1: Check trigger existence in optimizing creator

[mederly]

  Branch: refs/heads/master
  Home:   https://github.com/Evolveum/midpoint
  Commit: 2c94f1a4c404e6f7abd9357f6f48fcb950ad77f4
      https://github.com/Evolveum/midpoint/commit/2c94f1a4c404e6f7abd9357f6f48fcb950ad77f4
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2024-08-07 (Wed, 07 Aug 2024)

  Changed paths:
    M model/model-api/src/main/java/com/evolveum/midpoint/model/api/expr/MidpointFunctions.java
    M model/model-api/src/main/java/com/evolveum/midpoint/model/api/expr/OptimizingTriggerCreator.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/expr/MidpointFunctionsImpl.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/expr/triggerSetter/OptimizingTriggerCreatorImpl.java
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/TestOptimizingTriggerCreator.java

  Log Message:
  -----------
  Check trigger existence in optimizing creator

The OptimizingTriggerCreator did not check for trigger existence
in a strict way, which lead to creation of duplicate triggers
on some occasions - e.g., in cluster or when caches were cleared
in the meanwhile.

Although not considered harmful initially, it seems that this
behavior can lead to relatively massive creation of triggers
in some environments.

Hence, this commit strengthens the trigger existence checks,
at the cost of some extra repository read accesses.

Related to MID-9368.



To unsubscribe from these emails, change your notification settings at https://github.com/Evolveum/midpoint/settings/notifications