Don't set ACLs on potentially non-existing path /etc/tags (#2547)

This closes #2546
Adobe-Consulting-Services · Mar 14, 2021 · e1d6743 · e1d6743
1 parent 4e173f2
commit e1d6743
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -9,6 +9,9 @@ The format is based on [Keep a Changelog](http://keepachangelog.com)
 <!-- Keep this up to date! After a release, change the tag name to the latest release -->
 [unreleased changes details]: https://github.com/Adobe-Consulting-Services/acs-aem-commons/compare/acs-aem-commons-4.7.2...HEAD
 
+### Fixed
+- #2546 - org.apache.sling.jcr.repoinit.RepositoryInitializer-aem-cs.config prevents repository startup of AEM Cloud Quickstart due to usage of /etc/tags
+
 ## 5.0.0 - 2021-03-13
 
 ### Changed

diff --git a/...apps/acs-commons/config/org.apache.sling.jcr.repoinit.RepositoryInitializer-aem-cs.config b/...apps/acs-commons/config/org.apache.sling.jcr.repoinit.RepositoryInitializer-aem-cs.config
@@ -19,7 +19,7 @@ end
 create service user acs-commons-remote-assets-service with path system/acs-aem-commons
 set ACL for acs-commons-remote-assets-service
     allow jcr:read, jcr:versionManagement, rep:write, crx:replicate on /content/cq:tags
-    allow jcr:read, jcr:versionManagement, rep:write, crx:replicate on /content/dam, /etc/tags
+    allow jcr:read, jcr:versionManagement, rep:write, crx:replicate on /content/dam
     allow jcr:read on /
 
     # If /etc/tags is used, these ACLs be set manually - if RepoInit defines this structure, it supersedes the use of /content/cq:tags