*** The wcm.io Project is closing down this JIRA Instance in favor of GitHub issues. ***
Please use the corresponding GitHub projects to report issues - or the mailing list for general discussion.
Symlink for default.farm and default.vhost must not be generated when using custom farm
Description
According to the comments in the default dispatcher farm and default vhost config, when you create a customized copy of the default one, the symlink to the default file must be removed from enabled_farms and enabled_vhosts
Major
According to the comments in the default dispatcher farm and default vhost config, when you create a customized copy of the default one, the symlink to the default file must be removed from enabled_farms and enabled_vhosts
Currently the role still sets the symlinks despite of having customized copies
conga-aem-definitions/conga-aem-definitions/src/main/roles/aem-dispatcher-cloud.yaml at develop · wcm-io-devops/conga-aem-definitions
https://github.com/wcm-io-devops/conga-aem-definitions/blob/develop/conga-aem-definitions/src/main/roles/aem-dispatcher-cloud.yaml#L267-L270
This causes the following warning in disaptcher log
Wed Oct 13 05:13:32.427882 2021 [dispatcher:warn] [pid 1:tid 139784568048456] [cm-xxxx-xxxx-aem-publish-xxxx] /etc/httpd/conf.dispatcher.d/enabled_farms/farms.any:136: parent already contains an item with label "publishfarm"Also only one of these farms gets loaded randomly which also causes problems like 404 when the default farm is loaded instead of project specific one