Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.

Front end pipeline support for multi-level configurations

Avatar

Level 6

9/29/23

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):  
2 Comments

Avatar

Administrator

10/12/23

@rampai 

Thanks for proposing this idea
 
This has been reported to the engineering under the internal reference SITES-16565. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
Status changed to: Investigating