[jira] [Commented] (SLING-10136) Sling Repo Init: Add option to delete paths

["Henry Kuijpers (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371300#comment-17371300 ] 

Henry Kuijpers commented on SLING-10136:
----------------------------------------

Provided PR here [~bdelacretaz]
* https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/20
* https://github.com/apache/sling-org-apache-sling-repoinit-parser/pull/13


> 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: 20m
>  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)