Hi Clément, Thanks for the quick answer.
Too bad that there is no built-in function. I think that it could be an interesting feature :) Would it be possible for you to share how you do this exactly? And regarding the <delete> condition, would it be possible to set some kind of global variable when starting the synchronization (ex : sourceEmpty = true/false) and then check this variable for each entry? Thanks Maxime De : lsc-users [mailto:[email protected]] De la part de Clément OUDOT Envoyé : 8 novembre 2017 10:21 À : [email protected] Objet : Re: [lsc-users] Clean phase protection Le 08/11/2017 à 16:17, Maxime Pelletier a écrit : Hi, We faced a situation last week where a bug in one of our system didn't populated the content of our source SQL table, leaving the table empty. When the clean phase got triggered, it read this empty table, and deleted all users :S Is there a mechanism to prevent clean phases to start when the source is empty? Maybe with a <delete> condition? P.S.: We have a good backup system so we could restore everything :) The delete condition is run for every entry, so it won't solve this problem. What we usually do is to run lsc in dry-run mode first, get number of modified entries and launch it only is this number is not too high. Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
