Details
-
New Feature
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
COmanage Registry 3.2.5 (Oyster Pearl MR5)
-
None
Description
This could be implemented as a Provisioner Plugin that maintains a simple ID+CO Person+Timestamp log (table) on each provisioning event, and an API that constructs the current outbound Person record on demand. The API could also be a separate (core) component that doesn't require a serial number or timestamp, and simply pulls the current version of a CO Person in a single, coherent record.
See also the Registry Extraction Pull API draft.