[
https://issues.apache.org/jira/browse/SLING-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401131#comment-17401131
]
Karl Pauls commented on SLING-10136:
------------------------------------
[~angela], I don't disagree - as I said, we already have these unfortunately.
The question is where do we take it from here. From my POV, we have two options
- namely,
1. keep enhancing repoinit until it grows into a "repomanage" DSLs (which may
or may not have certain features togglable via configuration)
2. provide a second DSL for the more upgrade/managment related tasks (which may
or may not be a superset of repoinit)
and [~enorman], I don't think it is about limiting somebody - it is a question
of what users can expect to be able todo with it. Thats why I personally don't
know about enabling/disabling part of the DSL via configuration - that would
make it hard for people to know if a given repoinit would work or not.
Overall, I'd be in favor of just providing a second DSL that is a superset of
repoinit if we where to support more upgrade tasks. We could even keep it in
the same bundle(s) - just effectively have it come from different sources like
a different configuration or something so that it is clear they are different
things.
> 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)
