Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.

Read-only repository access in Author and Publisher for all environments in AEMaaCS

Avatar

Level 4

6/10/24

Request for Feature Enhancement (RFE) Summary: Developers should have a read-only view of CRX/DE for debugging purposes
Use-case: Debug deployment issues, check paths and properties
Current/Experienced Behavior: Currently AEMaaCS has repository browser but it has limitations - It is sometimes not showing few paths/folders even though it is there in author/publisher. It requires separate access via developer console and not all developers may have access to that.
Improved/Expected Behavior: Simplifies read-only view of crx/de is a better way to provide access to author and publish repository. Developers should even have this in production so that issue resolution for production content issues or code deployment issues can be expedited.
Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS author and publish environments
Customer-name/Organization name: GSPANN Technologies
Screenshot (if applicable):  
Code package (if applicable):  
4 Comments

Avatar

Administrator

7/17/24

@pardeepg4829047 

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

Avatar

Level 4

7/21/24

@kautuk_sahni 

 

Repo-browser has limitations which i highlighted in the current behaviour while raising this idea.

Adding those limitations here again:

- It is sometimes not showing few paths/folders even though it is there in author/publisher i.e. it does not reflect the state of the repo in real time. Having read-only view of crx/de will do better justice and eliminate the need of having a separate repo-browser.

- It requires separate access via developer console and not all developers may have access to that.