What happens in case some repository paths are missing also a property value already have some value

Question

Hi,we are having Repository Initializer from Sling to perform some initial setup of eg paths and permissions: This is how I have {"scripts": ["create path (sling:Folder) /content/dam/brands/ceccatocluster","create path (nt:unstructured) /content/dam/brands/ceccatocluster/jcr:content","create path (cq:Page) /content/brands/ceccatocluster","create path (nt:unstructured) /content/brands/ceccatocluster/jcr:content","create group CeccatoCluster-template with path /home/groups/brandsv2","set ACL for CeccatoCluster-template 
 allow jcr:all on /conf/brandsv2/ceccatocluster 
end","add CeccatoCluster-template to group template-authors","create group CeccatoCluster-content with path /home/groups/brandsv2","set ACL for CeccatoCluster-content 
 allow jcr:all on /content/brands/ceccatocluster 
end","set ACL for CeccatoCluster-content 
 allow jcr:all on /content/dam/brands/ceccatocluster 
end","add CeccatoCluster-content to group contributor","add CeccatoCluster-content to group workflow-users","set properties on /content/brands/ceccatocluster/jcr:content 
 set cq:allowedTemplates{String[]} to "/conf/brandsv2/ceccatocluster/settings/wcm/templates/(?!xf-).*" 
 set cq:conf{String} to /conf/brandsv2/ceccatocluster 
 set cq:deviceGroups{String[]} to /etc/mobile/groups/archetype 
 set cq:redirectTarget{String} to /content/brands/ceccatocluster/en 
 set cq:template{String} to /conf/brandsv2/ceccatocluster/settings/wcm/templates/content-page 
 set jcr:title{String} to "Ceccato Cluster" 
 set scene7Enabled{Boolean} to true 
 set sling:configRef{String} to /conf/brandsv2/ceccatocluster 
 set sling:redirect{Boolean} to true 
 set sling:redirectStatus{Long} to 302 
 set sling:resourceType{String} to brandsv2/components/structure/page 
end"]} what happens if in case some repository paths are missing, in case some of the properties already have some value (single value / multi value), etc.is there anyway to check if the property has this value set this, if the path is missing what to do in order to not effect repositoy initializer.Please share some inputs how we can improve the config files. Thanks,Vani.

EstebanBustamante · Accepted Answer

Hi @vani1012 ,

The repo-init runs before the SlingRepository service is registered, which briefly means that it will run before your code runs and usually, it is used as an "initial" setup for your code to work properly.

According to the official documentation, these are the preferred scenarios for the usage of repo-init:

Create/delete/disable service users
Create/delete groups
Create/delete users
Add ACLs

There is a a big NOTE also, You must create the path statements you will be using in your repoinit configurations, because they won't be available at the time the config runs.

You could also test what happen with your repoinit configurations by adding a custom logger and check how these will affect your repository. Add an INFO logger for the packages:

org.apache.sling.repoinit
org.apache.sling.jcr.repoinit

Here are good resources to deep dive into the understanding of how and when to use the repo init:

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/deploying/overview.html?lang=en#repoinit

https://www.bounteous.com/insights/2021/11/16/adobe-experience-managers-sling-repoinit-when-should-you-use-it

https://www.bounteous.com/insights/2021/11/16/adobe-experience-managers-sling-repoinit-have-you-tried-it-yet

aanchal-sikka · Answer

Hello @vani1012

The entire concept of repo-init fits the concept of mutable and immutable area.

This is generally used in context of AEM as a Cloud Service (AaaCS).

For ACLs defined for nodes underneath /apps or /libs the repoinit, execution starts on a blank repository. The packages are installed after repoinit so statements cannot rely on anything defined in the packages but must define the preconditions like the parent structures underneath.

In AaaCS, since the repoinit works on a blank repository, you don't have conflicts around arrays. However, the situation changes in case of AEM 6.5.

- All paths, code and content already exists.

So, when repo-init runs on start up we see issues related to arrays.

This would have been resolved if we were able to enforce arrays. Currently, it is only working for multiple values. Example following is documented on https://sling.apache.org/documentation/bundles/repository-initialization.html

set properties on /forcedMultiValue
  set singleMultiValue{String[]} to "single"
  set emptyMultiValue{String[]} to
  set singleLongMultiValue{Long[]} to 1243
  set emptyLongMultiValue{Long[]} to
end

Requesting you to please raise 2 support tickets for following:

Unable to enforce array for single values via repo-init
To explain how failures in repo-init are affecting your startup. This is more like an FYI to the team.

For more debugging, @estebanbustamante has shared more info with us

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded