[
https://issues.apache.org/jira/browse/SLING-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401506#comment-17401506
]
Karl Pauls commented on SLING-10136:
------------------------------------
[~enorman], funny, and maybe I wasn't expressing that in a clear enough way but
believe it or not, I don't think it is contradicting. For me, it is a question
about the scope of repoinit. Right now, that is rather limited as it isn't yet
a full upgrade DSL. Whether we want to change the scope to that or not is the
question. It's not the case that we are talking about limiting somebody to not
delete a path in general. If we want repoinit to grow in that direction I don't
see an issue with a delete/move/whatever path. Otherwise, I think it is not in
scope.
I agree with [~cziegeler]s summary above - we have these 3 choices (plus maybe
the option to the second one that we could start a new language altogether with
a maybe better suited approach like e.g. declarative, rather then imperative,
statements - if we think that would make more sense than making it a superset
of the current repoinit).
> Sling Repo Init: Add option to delete paths
> -------------------------------------------
>
> Key: SLING-10136
> URL: https://issues.apache.org/jira/browse/SLING-10136
> Project: Sling
> Issue Type: New Feature
> Components: Repoinit
> Affects Versions: Repoinit Parser 1.6.4, Repoinit JCR 1.1.30
> Reporter: Henry Kuijpers
> Priority: Major
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Given that we are able to create paths, it would also be beneficial to be
> able to delete paths as well.
> In our case, we're migrating a legacy setup to Sling Repo Init, where there
> are some "leftover" nodes in the instances. Given that Sling Repo Init is an
> "admin" way to initialize a repo, it would be very nice if delete statements
> could be supported.
> In our case, we would want to delete /apps/foundation, for example, because
> historically there seem to have been modifications made there.
> This mandates for a simple syntax like "delete path /apps/foundation" being
> supported.
> Another case is that we would like to cleanup /apps/cq, however, there are
> some nodes that are maintained by the product (in our case AEM), such as
> /apps/cq/xssprotection and also /apps/cq/core/content/nav/tools.
> This mandates for a slightly more complicated syntax such as "delete path
> /apps/cq (!/xssprotection,!/core/content/nav/tools,*)", however, I would be
> fine with multiple delete path statements as well, for that usecase.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
