The MCUBoot related configuration in cmake is scattered across multiple files (e.g. CommonConfig.cmake, MCUBootConfig.cmake, <XY_platform.cmake>).
It is difficult to ensure/maintain the consistency of configuration in this form; there are dependencies between the platforms, upgrade strategies and the number of
separately updatable images too. The configuration of MCUBoot should be handled in a more centralized way, for example instead of modifying the bootloader related
variables in the platform cmake files, the platform could define the lists of supported options and pass them as input parameters to cmake functions (defined in
MCUBoot.cmake for example). This way it would be the MCUBoot cmake "module" 's responsibility to ensure a consistent configuration.