Clientlibs: Long Cache Config to support hash for AEM on-prem - Status changed to: Needs Info

[#1]

Request for Feature Enhancement (RFE) Summary:	Support long term cache config to generate a hash each time clientlibs are modified for AEM on-prem instance.
Use-case:	Currently, we have to use ACS commons for long term cache config and that has lot of deprecated APIs and more features than required. So can Adobe add the feature of 'hash' for on-prem instances similar to AEM Cloud - beyond auto and none? [com.adobe.granite.ui.clientlibs.impl.LongCacheConfig]
Current/Experienced Behavior:	It generates a longtermkey based on system time of the service restart.
Improved/Expected Behavior:	Generate a new key based on last modification of clientlibs to make it dynamic.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM 6.5.5
Customer-name/Organization name:	TA Digital
Screenshot (if applicable):
Code package (if applicable):

[#2]

Refer link for AEM Cloud https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/content-delive...

[#3]

Hi @Chetanyajain1 

Did you get a chance to verify the provided document where the same feature is discussed ?

[#4]

Hi @hamidk92094312 this feature is only on AEM Cloud version and is not present for on-prem (6.5.5) version. Hence requesting the same feature to be made available for the on-prem.

Also, did you share any documentation link?

[#5]

Hi @Chetanyajain1 

This request has been raised to the product team via the Jira CQ-4316688. The product team will triage this request to verify feasibility based on prioritization model. This post will be updated according to the Jira request status.

[#6]

Thank you @hamidk92094312 

[#7]

@Chetanyajain1 This feature will be limited to AEM CS in the future. So, marking this as Declined as of now.

Thank you for your feedback on this.