Product ideas | Community
Skip to main content

10000 Ideas

rampai
rampaiNew Participant

Front end pipeline support for multi-level configurationsInvestigating

Request for Feature Enhancement (RFE) Summary: Front-end pipeline (FEP) configuration can only be set at root level of the site in content hierarchy. Also, the sling:configs can be added directly under /conf and not a node beneath. Use-case: We have grouped our sites and are looking for separate front end pipelines per site.  e.g. /content/group1/site1, /content/group1/site2, /content/group2/site1, /content/group2/site2 Similarly for sling:configs: /conf/group1/site1, /conf/group1/site2, /conf/group2/site1, /conf/group2/site2 Current/Experienced Behavior: Front-end pipeline (FEP) configuration can only be set at root level of the site. i.e /content/group1 - FEP1 or /content/group2 - FEP2 Similarly for sling:configs: /conf/group1, /conf/group2 Improved/Expected Behavior: Front-end pipeline (FEP) configuration can be set at multiple levels within the content tree. i.e /content/group1/site1 - FEP1, /content/group1/site2 - FEP2, /content/group2/site1 - FEP3, /content/group2/site2 - FEP4   Similarly for sling:configs: /conf/group1/site1, /conf/group1/site2, /conf/group2/site1, /conf/group2/site2 Environment Details (AEM version/service pack, any other specifics if applicable): AEM as Cloud service latest release Customer-name/Organization name: Abbott Screenshot (if applicable):   Code package (if applicable):