Currently the ELB listener priorities set for the new civic-2017 and civic-2018 services place them after last years services rules. Since last years service rules do not have host domain/sub-domains set, they match before this years services rules are reached.
Quick fix (which was done manually) was to change the rule ordering so that the new 2018 service rules are placed before all of the 2017 services rules. This can be done permanently in the service.yaml templates for the new services.
An alternative would be to assign doamin/sub-domain entries to last years (2017) services to have civicpdx.org so that their rules would only match when the path is civicpdx.org/something.
Currently the ELB listener priorities set for the new civic-2017 and civic-2018 services place them after last years services rules. Since last years service rules do not have host domain/sub-domains set, they match before this years services rules are reached.
Quick fix (which was done manually) was to change the rule ordering so that the new 2018 service rules are placed before all of the 2017 services rules. This can be done permanently in the service.yaml templates for the new services.
An alternative would be to assign doamin/sub-domain entries to last years (2017) services to have civicpdx.org so that their rules would only match when the path is civicpdx.org/something.