Issues
- Symlink for default.farm and default.vhost must not be generated when using custom farmWDCONGA-31Resolved issue: WDCONGA-31Stefan Seifert
- How run-modes are supported for CONGA Environments for AEM Cloud?WDCONGA-30Resolved issue: WDCONGA-30
- Rename publish.farm to publish.anyWDCONGA-29Resolved issue: WDCONGA-29
- wrong dispatcher filter rules for role my-aem-dispathcerWDCONGA-28Resolved issue: WDCONGA-28Stefan Seifert
- Add support for custom configuration options outside the virtualhost sectionWDCONGA-27
- Optimization of modRemoteIP ConfigurationWDCONGA-26
- Handelbars EnsurePropertiesHelper do not support global propertiesWDCONGA-25Resolved issue: WDCONGA-25
- Configuration of secondary variant are not appliedWDCONGA-24Resolved issue: WDCONGA-24
- Sample config for experiencecloud on azureWDCONGA-23
- Apply sling mapping only on publish runmodeWDCONGA-22Resolved issue: WDCONGA-22
- Sling mapping rewrites URLs of tenants without mappingWDCONGA-21Resolved issue: WDCONGA-21Stefan Seifert
- Support expression language in CONGA variable expressionsWDCONGA-20Resolved issue: WDCONGA-20Stefan Seifert
- Location Directive in vhost_author.partials.hbs not properly closedWDCONGA-19Resolved issue: WDCONGA-19Stefan Seifert
- Distro-agnostic file layout for aem-dispatcher roleWDCONGA-18Resolved issue: WDCONGA-18
- Minimize duplication between multiple environmentsWDCONGA-17Resolved issue: WDCONGA-17
- Value Processors for CONGAWDCONGA-16Resolved issue: WDCONGA-16
- Value Providers for CONGAWDCONGA-15Resolved issue: WDCONGA-15
- AEM Definitions: Aggregate dispatcher author/publish/common into a single roleWDCONGA-14Resolved issue: WDCONGA-14
- Conditional Role Configuration/More Flexible VariantsWDCONGA-13Resolved issue: WDCONGA-13
- Generate Access Rules from Role ConfigurationWDCONGA-12Resolved issue: WDCONGA-12
- Generate AEM Content Package with binary propertiesWDCONGA-11Resolved issue: WDCONGA-11
- Parameters cannot be used in tenant namesWDCONGA-10Resolved issue: WDCONGA-10
- Control item ordering when merging parameter value listsWDCONGA-9Resolved issue: WDCONGA-9
- Mandantory Parameters for RolesWDCONGA-8Resolved issue: WDCONGA-8
- NullPointerException with malformed Maven URL in roleWDCONGA-7Resolved issue: WDCONGA-7
- List merging with "_merge_" does not work properlyWDCONGA-6Resolved issue: WDCONGA-6
- generated sling configuration does not contain the variableWDCONGA-5Resolved issue: WDCONGA-5Guiquan Weng
- make dispatcher /clientheaders configurableWDCONGA-4Resolved issue: WDCONGA-4
- fix auto invalidation rules and default statfileslevel in publish dispatcher.anyWDCONGA-3Resolved issue: WDCONGA-3Stefan Seifert
- Introduce Node Role InheritanceWDCONGA-2Resolved issue: WDCONGA-2
- Find a way to automatically create Ops documentationWDCONGA-1
Symlink for default.farm and default.vhost must not be generated when using custom farm
Description
Details
Details
Assignee
Reporter
Components
Priority
Activity
Stefan SeifertOctober 26, 2021 at 11:54 AM
thanks, PR is merged
Masoud RozatiOctober 22, 2021 at 10:53 AM
I adjusted the ticket title because we should also remove the default.vhost symlink.
If those two symlinks are removed the error is solved. We just tested it.
Nico BellackOctober 18, 2021 at 2:45 PM
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
This also happens for me. vanity_urls
are deactivated by default in the default_farm file. Activating it in the project-specific file isn’t recognized since the default file gets loaded instead.
Masoud RozatiOctober 18, 2021 at 10:41 AM
Pull request for the solution:
https://github.com/wcm-io-devops/conga-aem-definitions/pull/70
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
https://github.com/wcm-io-devops/conga-aem-definitions/blob/develop/conga-aem-definitions/src/main/roles/aem-dispatcher-cloud.yaml#L243-L246
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