[
https://issues.apache.org/jira/browse/SLING-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932607#comment-16932607
]
Robert Munteanu commented on SLING-8619:
----------------------------------------
Thanks for the patches [~angela], I think I managed to cover all dependencies
and can start looking at this one now :-) . One thing that stands out on a
cursory review is the usage of {{null}} to mean 'whole repository'. Maybe we
can use something more descriptive like 'repository'? I assume that we never
use relative paths here.
As for the documentation, what we have is at
https://github.com/apache/sling-site/blob/master/src/main/jbake/content/documentation/bundles/repository-initialization.md
.
/cc [~bdelacretaz] for the discussion on using null as the repository marker.
> RepoInitGrammer: Add repository-level marker to pathsList
> ---------------------------------------------------------
>
> Key: SLING-8619
> URL: https://issues.apache.org/jira/browse/SLING-8619
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Reporter: angela
> Assignee: Robert Munteanu
> Priority: Major
> Attachments: SLING-8619-jcr.patch, SLING-8619-parser.patch
>
>
> In order to be able to cover repository level access control entrieswith the
> {{PrincipalAccessControlList}} (see SLING-8602), i would like to expand the
> {{RepoInitGrammer.pathsList()}} such that it not only handles absolute paths
> but in addition a marker for the repository level permissions (in JCR marked
> with a _null_ path).
> essentially this would also create an alternative way to edit policies for
> the _null_ path (today covered with _set repository ACL ..._).
> will provide a proposed patch and tests later this week.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
