Apply sling mapping only on publish runmode
Description
Activity
Show:
Stefan Seifert March 15, 2019 at 11:01 PM
agreed, it's reverted

Tobias Richter March 15, 2019 at 7:04 PM
Revert requsted with: https://github.com/wcm-io-devops/conga-aem-definitions/pull/44
See also discussion in https://github.com/wcm-io-devops/conga-aem-definitions/pull/41
Stefan Seifert March 12, 2019 at 10:10 PM
yes this makes sense - merged

Masoud Rozati March 12, 2019 at 1:39 PM
Won't Fix
Details
Details
Assignee
Unassigned
UnassignedReporter

Components
Priority
Created March 12, 2019 at 1:34 PM
Updated March 15, 2019 at 11:01 PM
Resolved March 15, 2019 at 11:01 PM
In order to prevent deploying publish sling mapping on author by mistake, we should change the path from
/etc/map
to/etc/map.publish
See also the recommendation at the bottom of this page:
https://helpx.adobe.com/experience-manager/6-4/sites/deploying/using/resource-mapping.html
Of course this should not happen if the CONGA role is used, but currently on AMS uses a manual approach to install packages. Having runmode in the mapping would make it safer.