Bug fix (non-breaking change which fixes an issue)
Description
Enhance the routine used to determine what level of property override should apply to handle three levels. While re-ordering
its parameters would make them more logical, add support for the extra level to the end to minimise the scope of the change.
Configure the account mapping logic to use this new capability.
Account mappings can have up to three levels of override - PRODUCT, ENVIRONMENT, SEGMENT. The current logic doesn't correctly support all combinations.
How Has This Been Tested?
manual testing of the findAndDefineSetting function
testing (post merge) at customer site where issue has arisen
Intent of Change
Description
Enhance the routine used to determine what level of property override should apply to handle three levels. While re-ordering its parameters would make them more logical, add support for the extra level to the end to minimise the scope of the change.
Configure the account mapping logic to use this new capability.
Motivation and Context
Fixes https://github.com/hamlet-io/engine/issues/1992
Account mappings can have up to three levels of override - PRODUCT, ENVIRONMENT, SEGMENT. The current logic doesn't correctly support all combinations.
How Has This Been Tested?
findAndDefineSettingfunctionRelated Changes
Prerequisite PRs:
Dependent PRs:
Consumer Actions: