[midPoint-git] [Evolveum/midpoint] ae3792: Treat refs in unclassified shadows gracefully

[mederly]

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

  Changed paths:
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/TestIntent.java
    M provisioning/provisioning-impl/src/main/java/com/evolveum/midpoint/provisioning/impl/ProvisioningContext.java
    M provisioning/provisioning-impl/src/main/java/com/evolveum/midpoint/provisioning/impl/RepoShadow.java
    M provisioning/provisioning-impl/src/test/java/com/evolveum/midpoint/provisioning/impl/dummy/TestDummyIntents.java

  Log Message:
  -----------
  Treat refs in unclassified shadows gracefully

When legacy associations are present, and the association definition
is not visible in the object class, the following may occur:

When storing repo shadows with references, the shadow gets unreadable:
it contains the reference, e.g., because it was read from resource
with kind/intent known, but the created shadow has only object class
name, not the kind+intent (as the classification was not done yet).

This commit introduces special lax mode that ignores the references
when parsing such shadows. (With a little hack related to ignoring
empty reference attributes that should not be there; repo should take
care of that.)

This fixes TestIntents running with shadow caching enabled.



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