[
https://issues.apache.org/jira/browse/SLING-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16133014#comment-16133014
]
Timothee Maret commented on SLING-6984:
---------------------------------------
[~bdelacretaz] I re-ran the IT tests successfully locally. Could it be that
Jenkins reference an "old" SNAPSHOT or either
org.apache.sling/org.apache.sling.repoinit.parser or
org.apache.sling/org.apache.sling.jcr.repoinit ?
Regarding the behaviour when invoking the disable user on a non existing user,
we could indeed make it pass and log rather than throw an exception. I did
throw an exception to be consistent with the delete user operation (for which
we may apply the same reasoning).
> Allow to disable service user
> -----------------------------
>
> Key: SLING-6984
> URL: https://issues.apache.org/jira/browse/SLING-6984
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Affects Versions: Repoinit Parser 1.1.0, Repoinit JCR 1.1.4
> Reporter: Timothee Maret
> Assignee: Timothee Maret
> Fix For: Repoinit Parser 1.1.2, Repoinit JCR 1.1.6
>
>
> Currently the repoinit module does not support -removing- disabling service
> users.
> Disbling -Removing- service user is required when one user is no longer
> needed due to service user sharing among components.
> The syntax could be the one proposed by [~anchela]
> {code}
> disable service user <serviceUserId> <disableMessage>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
