Rename publish.farm to publish.any
Description
Activity
Stefan Seifert June 17, 2020 at 2:08 PM
probably we need a new role for AMS cloud manager dispatcher config, which incorporates the differences. ideally the configuration is the same, so it's a drop-in replacement which role is chosen.
Stefan Seifert June 17, 2020 at 10:51 AMEdited
it has the same naming (.farm extension) in the adobe archetype
https://github.com/adobe/aem-project-archetype/tree/master/src/main/archetype/dispatcher.cloud/src/conf.dispatcher.d
but you're right, the adobe archetype has a parallel directory for AMS dispatcher config which seems to use different naming
https://github.com/adobe/aem-project-archetype/tree/master/src/main/archetype/dispatcher.ams/src/conf.dispatcher.d
unfortunately those both config sets do not seem to be synchronized. i'm wondering if there are more difference between those too - would be good to support both in CONGA AEM definitions.
there is a conversion tool to convert AMS dispatcher config to cloud dispatcher config
https://docs.adobe.com/content/help/en/experience-manager-cloud-service/moving/refactoring-tools/dispatcher-transformation-utility-tools.html
https://github.com/adobe/aem-cloud-service-dispatcher-converter
maybe we can reverse-engineer the differences from this converter tool.
Details
Details
Assignee
Reporter
Tobias RichterComponents
Priority
Minor
I used the aem-dispatcher-cloud role in an ams basic project and I was stumbling over several things. One item is the "publish.farm" file.
I see that this is coming from the cloud sdk and I am wondering if we can rename the file from publish.farm to publish.any.
At the moment we are renaming the file before deploying it to the AMS basic instance. The client is using dispatcher 2.1 layout and there are no .farm files used. I am wondering if this might be an issue with the dispatcher cloud sdk.