[ https://issues.apache.org/jira/browse/SYNCOPE-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190935#comment-15190935 ]
ASF subversion and git services commented on SYNCOPE-771: --------------------------------------------------------- Commit 61a7fdd38e412a30eeb24161400c669a2c3f3228 in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=61a7fdd ] [SYNCOPE-771] Rename completed > Rename Sync to Pull > ------------------- > > Key: SYNCOPE-771 > URL: https://issues.apache.org/jira/browse/SYNCOPE-771 > Project: Syncope > Issue Type: Improvement > Reporter: Francesco Chicchiriccò > Assignee: Francesco Chicchiriccò > Fix For: 2.0.0 > > > Rename all Sync* things (throughout the whole system) to Pull, for a couple > of reasons: > # the word "synchronization" evokes some kind of bidirectional flow, while > instead we intend pulling users, groups and any objects from external > resources by relying on either {{search()}} or {{sync()}} ConnId operations > # we are already using "push" for the opposite operation > Moreover, it would be good, once changed all references, to include a > "synchronization use case" in the documentation from SYNCOPE-700, which > involves creating a pull task with assign matching request so that, for > example, users pulled from LDAP will also be automatically assigned the LDAP > resource. -- This message was sent by Atlassian JIRA (v6.3.4#6332)