[midPoint-git] [Evolveum/midpoint] cf3a69: Relax parsing stale repo shadows

[mederly]

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

  Changed paths:
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/processor/ShadowAssociationValue.java
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/processor/ShadowAttributesContainer.java
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/processor/ShadowDefinitionApplicator.java
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/processor/ShadowReferenceAttributeValue.java
    M infra/schema/src/main/java/com/evolveum/midpoint/schema/util/ShadowUtil.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/main/java/com/evolveum/midpoint/provisioning/impl/ResourceObjectFuturizer.java
    M provisioning/provisioning-impl/src/main/java/com/evolveum/midpoint/provisioning/impl/shadows/ShadowModifyOperation.java
    M provisioning/provisioning-impl/src/test/java/com/evolveum/midpoint/provisioning/impl/opendj/TestOpenDj.java
    M provisioning/provisioning-impl/src/test/resources/opendj/resource-opendj-no-read.xml
    M provisioning/ucf-impl-builtin/src/main/java/com/evolveum/midpoint/provisioning/ucf/impl/builtin/async/update/TransformationalAsyncUpdateMessageListener.java

  Log Message:
  -----------
  Relax parsing stale repo shadows

When resource schema changes in an incompatible way, schema issues can
occur during repo shadow reading. This commit tries to deal with that:

- On one hand, we want to work with the correct data. Even skipping
unreadable items can lead to a disaster, e.g., if there are mappings
that propagate this information further.

- On the other hand, we do not want to fail hard when the resource
schema changes.

The probably simplest solution is to be strict for fresh shadows,
but more relaxed for stale ones: the data will not be used anyway
(except for the identifiers - but they do not change as frequently).

The general recommendation will be: after you change the schema, please
invalidate the cache.

This fixes a couple of provisioning tests.



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