[midPoint-git] [Evolveum/midpoint] 1595f1: Avoid deleting proposed shadows
mederly
noreply at github.com
Sat Nov 11 13:34:17 CET 2023
Branch: refs/heads/feature/attribute-caching
Home: https://github.com/Evolveum/midpoint
Commit: 1595f11b4aa9efbcbd39648415c722c1c2bd73f8
https://github.com/Evolveum/midpoint/commit/1595f11b4aa9efbcbd39648415c722c1c2bd73f8
Author: Pavol Mederly <mederly at evolveum.com>
Date: 2023-11-11 (Sat, 11 Nov 2023)
Changed paths:
M infra/schema/src/main/java/com/evolveum/midpoint/schema/processor/ResourceObjectIdentifiers.java
M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/TestConsistencySimple.java
M provisioning/provisioning-impl/src/main/java/com/evolveum/midpoint/provisioning/impl/resourceobjects/ResourceObjectConverter.java
M provisioning/provisioning-impl/src/main/java/com/evolveum/midpoint/provisioning/impl/shadows/ShadowDeleteOperation.java
Log Message:
-----------
Avoid deleting proposed shadows
Shadows in PROPOSED state are certainly not present on the resource.
Moreover, their deletion should fail because (among others factors)
they usually do not have a primary identifier.
This commit makes sure we do not even attempt deletion of these objects.
This fixes broken TestConsistencySimple and TestMultiResource after
f59d5f7c2ab0722c95bc0c977a80d70f8440cd53.
More information about the midPoint-svn
mailing list