[
https://issues.apache.org/jira/browse/SLING-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812131#comment-15812131
]
Bertrand Delacretaz commented on SLING-6423:
--------------------------------------------
IIUC your patch suggests using a {noformat}merge{...}{noformat} block to
specify ACL statements that should be merged?
I think options in parentheses are more in line with the existing repoinit
syntax:
{code}
set ACL for alice, bob,fred (ACLoptions=merge)
allow jcr:read on /content,/var
deny jcr:write on /content/example.com
deny jcr:all on / nodetypes example:Page
end
{code}
would that work for your use cases?
> Allow for specifying ACL merge mode (ACHandling) in repoinit
> ------------------------------------------------------------
>
> Key: SLING-6423
> URL: https://issues.apache.org/jira/browse/SLING-6423
> Project: Sling
> Issue Type: New Feature
> Components: Repoinit
> Reporter: Nitin Nizhawan
> Attachments: SLING-6423_testcases.patch
>
>
> Repoinit by default just add new ACLs if they are not already present.
> By contract package manager provides various strategies for ACL merging
> Extend repoinit to allow specifying these strategies
> https://jackrabbit.apache.org/filevault/apidocs/org/apache/jackrabbit/vault/fs/io/AccessControlHandling.html#MERGE
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
