Hi, We have been testing Syncope CLI and especially the tasks execute and list command, and we have encountered a few problems: - When we tried running "./syncopeadm.sh --list PULL" or "./syncopeadm.sh --list PULL", it listed the runs, but the output was old, dated Nov. 6 and Nov. 7 (today is Nov. 20). In other words, the output from the "–list PULL" and "–list PUSH" commands seems to be stuck and not recording current statuses, I think.
- The CLI tasks commands use a task "key" to identify each task. The task "key" is a long hex-like string, and is probably not memorizable. Also, so far, the only way that I have been able to find the task "key" for a given task is to review the output from the --list PULL" or "–list PUSH" commands, which may also be problematic. Is it possible to use the task names instead of the task "key" when running commands? Slightly different area: - We accidentally mapped a single internal attribute, "dutyOrg" to 2 different external attributes, "co" and "dutyOrg" on a target LDAP. However, when we ran the pull task followed by the push task, only the "co" attribute in the target LDAP instance was changed. In other words, the mapping from the one internal attribute to two different external attributes didn't appear to work. For us, if this is the case, this would be a MAJOR problem, as in the current product we use, we have many attribute flows where a single attribute is pushed to multiple attributes in the target LDAPs. Please advise if there are any ways to workaround the above problems? Thanks,Jim
