[midPoint-git] [Evolveum/midpoint] 7dc4c9: Add methods to find resource and linked/correlated...

[Andrej]

  Branch: refs/heads/feature/t-4184
  Home:   https://github.com/Evolveum/midpoint
  Commit: 7dc4c95281cb0e9646b9338a745ea788de2d9d9c
      https://github.com/Evolveum/midpoint/commit/7dc4c95281cb0e9646b9338a745ea788de2d9d9c
  Author: Andrej Zan <andrej.zan at evolveum.com>
  Date:   2026-02-17 (Tue, 17 Feb 2026)

  Changed paths:
    M model/model-api/src/main/java/com/evolveum/midpoint/model/api/correlation/CorrelationService.java
    M model/model-impl/src/main/java/com/evolveum/midpoint/model/impl/correlation/CorrelationServiceImpl.java
    M provisioning/provisioning-api/src/main/java/com/evolveum/midpoint/provisioning/api/ProvisioningService.java

  Log Message:
  -----------
  Add methods to find resource and linked/correlated focus

**What**

Add two new method. One to find the resource to which the given shadow
belong, second which finds the linked/correlated focus of the given
shadow.

**Why**

- The method for finding resource seems to be useful in general.
- The method to find linked/correlated focus of the shadow will be used
  in the simulation of mappings. Similar method, which searches for
  linked user already exists in the `RepositoryService`, but it is
  deprecated and it does only one half of this new method.

**Task**: 10992


  Commit: 84726e3c3ca3362c88d37959dfa4af7632cae689
      https://github.com/Evolveum/midpoint/commit/84726e3c3ca3362c88d37959dfa4af7632cae689
  Author: Andrej Zan <andrej.zan at evolveum.com>
  Date:   2026-02-17 (Tue, 17 Feb 2026)

  Changed paths:
    M model/model-intest/src/test/resources/tasks/correlator-simulation/task-correlator-simulation-with-mapping.xml
    M model/model-intest/src/test/resources/tasks/correlator-simulation/task-correlator-simulation.xml

  Log Message:
  -----------
  Fix initial state of tasks used in tests.

**What**

Fix the initial state of tasks from `runnable` to `closed` to prevent
unintended start of the tasks after import.

**Task**: 11031


  Commit: 4ebfec3343a2288fb9d07a26db9c3030be9f0d7c
      https://github.com/Evolveum/midpoint/commit/4ebfec3343a2288fb9d07a26db9c3030be9f0d7c
  Author: Andrej Zan <andrej.zan at evolveum.com>
  Date:   2026-02-17 (Tue, 17 Feb 2026)

  Changed paths:
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/tasks/TestCorrelatorSimulationTask.java
    M model/model-intest/src/test/resources/tasks/correlator-simulation/accounts.csv
    M model/model-intest/src/test/resources/tasks/correlator-simulation/dummy-resource.xml
    A repo/repo-test-util/src/main/java/com/evolveum/midpoint/test/AccountsCsvParser.java
    M repo/repo-test-util/src/main/java/com/evolveum/midpoint/test/DummyTestResource.java
    A repo/repo-test-util/src/main/java/com/evolveum/midpoint/test/ObjectChangesExecutor.java
    A repo/repo-test-util/src/main/java/com/evolveum/midpoint/test/ShadowReader.java
    A repo/repo-test-util/src/main/java/com/evolveum/midpoint/test/TestResourceAccounts.java

  Log Message:
  -----------
  Add new resource/account related testing framework APIs

**What**

Add new API to the `DummyTestResource`:

- To create a dummy resource populated with accounts from CSV file.
- To link/correlate accounts in the resource with provided users.

**Why**

Very similar functionality was already implemented in various places
across various tests causing duplicity. This changes tries to "unify"
the implementation and provide a good place for such functionality.

Given that the functionality is highly related to the resource, I
decided to put it to the `DummyTestResource` class.

The new `TestResourceAccounts` is intended to represent all accounts on
the resource. So far it only contains two methods, but it can be
extended on demand.

**Note**

Current implementation is not as clean as it could be, because we are
(currently) limited by the fact that `DummyTestResource` is defined in
the repository module, thus it does not have access to some
functionalities implemented in the other modules (e.g. provisioning or
model-intest).

If we will be sometimes able to move this classes e.g. to provisioning,
it will be possible to simplify the API (by removing some of the
functional interfaces).

**Task**: 10992


Compare: https://github.com/Evolveum/midpoint/compare/7dc4c95281cb%5E...4ebfec3343a2

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