Tombstones are deleted entries which are stored for some time in case they are needed for conflict resolution. Normally they should not be touched by client applications, but if an entry was deleted "unintentionally" it would be helpful to be able to "undo" this. Either provide a description how it could be achieved by standard ldap operations or provide a specific method (task?) to do this
Metadata Update from @lkrispen: - Issue set to the milestone: FUTURE
Add to dsconf? Make Admin's lives easier?
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: None - Issue set to the milestone: 1.4.4 (was: FUTURE)
I think there is already some functions in lib389 to recreate a new entry from a tombstone, but it's not true revival.
Honestly, this is probably closer to a recyclebin feature, and could be better to implement that instead of potentially messing with the replication framework too much.
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/736
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.