Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-10972

Backport OPENIDM-9643: Separate the logic out for storing the 'lastSync' property out of the all-inclusive ManagedObjetSet#update

    Details

      Description

      Currently when we add the 'lastSync' property to a managed user we call the ManagedObjectSet#patchInstance to update the managed/user object with this property and that in turn calls out to ManagedObjectSet#update(. This update does a bunch of no-op related to relationships that it should not care about because only the 'lastSync' property should be modified with this 'snapshot' of that last 'effectiveRoles' and 'effectiveAssignments' that were last successfully sync'd out to the associated mappings.

      To clear things up, lets move all the logic necessary to patch the managed object with the 'lastSync' property out into a separate method. This will be easier to replace when the queued sync becomes something tangible.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mark.offutt Mark Offutt
                Reporter:
                mark.offutt Mark Offutt
                QA Assignee:
                Jakub Janoska
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: