[
https://issues.apache.org/jira/browse/SLING-6984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16133021#comment-16133021
]
Bertrand Delacretaz commented on SLING-6984:
--------------------------------------------
The ITs do pass as is, they fail if I apply the above patch, which tries to
disable a non-existing service user.
I agree that the behavior that I suggest is not consistent with "delete user".
[~anchela] WDYT, should an attempt to disable a service user that does not
exist cause a failure, or just an informational log message but not failure?
Note that the SlingRepository service will not start if there are any repoinit
failures.
> 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)
