Expand my Community achievements bar.

Enhance OpenAPI Content Fragment for List Fragments

Avatar

Level 6

9/23/24

Request for Feature Enhancement (RFE) Summary: Enhance Content Fragment OpenAPI for List Fragments to include eTag
Use-case: List Content Fragment documentation reads, API would return `etag`.
sarav_prakash_0-1727139985720.png

But when testing against AEM, the etag field is missing in response.

sarav_prakash_1-1727140005227.png

This leads to a problem when updating CF, we dont have CF etag to pass into If-Match header. So update CF requires 3 trips:

  1. Find CF ID using List
  2. Find etag using Get
  3. Edit CF using Patch

Fixing List CF API to return eTag will reduce UpdateCF to 2 trips 

Current/Experienced Behavior: List CF API is NOT returning eTag in response
Improved/Expected Behavior: List CF API must return eTag in response 
Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS
Customer-name/Organization name: SGWS
Screenshot (if applicable): provided above
Code package (if applicable):  
1 Comment

Avatar

Administrator

10/8/24

@sarav_prakash Thanks for proposing this idea.

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