Issue #555 has been updated by Raphaël Ouazana. Assigned to changed from Sébastien Bahloul to Raphaël Ouazana
After some discussions, the solution that will be implemented is: - to not make any differences between dry-run and not dry-run while evaluating conditions - add a boolean flag dryRun in javascript context to allow to detect the dry run state, and so permit to migrate from strange configurations ---------------------------------------- Feature #555: Dry-run should consider <conditions> settings http://tools.lsc-project.org/issues/555 Author: Maxime Pelletier Status: Assigned Priority: Normal Assigned to: Raphaël Ouazana Category: Core Target version: 2.1 When running a task in dry-run (-n flag), then all modification possibilities are evaluated. It should consider <conditions> settings in lsc.xml file: <pre> <conditions> <create>false</create> <update>true</update> <delete>false</delete> <changeId>false</changeId> </conditions> </pre> In this example, LSC should only evaluate update, even in dry-run. I think that this change should be consider since dry-run could have external impact (java class or LSC function like SequencesFactory.getNextValue). -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
