[
https://issues.apache.org/jira/browse/SLING-7960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634061#comment-16634061
]
Bertrand Delacretaz commented on SLING-7960:
--------------------------------------------
bq. If we would have a language specification for repo init, we could create a
dependency towards it.
Good point! Although we don't have a formal specification, the releases of the
repoinit components do define a language + implementation version.
To stay backwards compatible I agree that repoinit scripts need to define which
version of the language + implementation they expect.
I have started a discussion about this on our dev list in the "How to manage
repoinit language + implementation evolutions?" thread.
> Repoinit: "delete user" also deletes service user
> -------------------------------------------------
>
> Key: SLING-7960
> URL: https://issues.apache.org/jira/browse/SLING-7960
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Affects Versions: Repoinit JCR 1.1.8
> Reporter: Jörg Hoh
> Priority: Major
> Attachments: SLING-7960-2.patch, SLING-7960-3.patch, SLING-7960.patch
>
>
> My current application uses a regular user, but with some changes to the
> framework we need to migrate to regular service users. The service user is
> being added as part of the deployment.
> To automate this I decided to use the repoinit to remove the regular user and
> then deploy the service user. Which works fine, but only until the next time
> the repoinit is executed again. Because then the repoinit statement
> {{delete user foo}}
> purges the newly created serviceuser "foo". Which is totally unexpected,
> because there is a dedicated command "delete service user" which is supposed
> to remove users. So "delete user foo" must only delete a regular user "foo"
> but not a service user named "foo".
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
