-
Bug
-
Resolution: Fixed
-
Neutral
-
6.2.27
-
None
-
None
-
-
Empty show more show less
-
AdminX 27
-
2
Context
- Defined "config.yaml" inside a folder located in "magnolia.resources.dir" e.g /magnolia-sso/config.yaml, with "magnolia-sso" is not (or no longer ^^) an existing/registered module name.
- ModuleConfigurationRegistry and YamlConfigurationSource try to load the config.yaml with the path pattern "$^/(?<module>[a-zA-Z0-9-_]+)/config
.yaml" (https://git.magnolia-cms.com/projects/platform/repos/main/browse/magnolia-configuration/src/main/java/info/magnolia/config/module/ModuleYamlConfigurationSource.java?at=f9fcb3cdd54f40849d38058e5f2afdfd3287d24c#54)Â even though the module name is not registered. - So it will throw an exception during start up:
2022-12-22 12:21:39,552 ERROR info.magnolia.event.SimpleEventBus : Exception caught when dispatching info.magnolia.module.PopulateModulesEvent with info.magnolia.config.module.ModuleConfigurationRegistry$$Lambda$483/0x0000000800843840 eventHandler. java.lang.IllegalArgumentException: No module registered with name "magnolia-sso".
- Full log from installation to startup 6.2_SSO_install_and_startup_error.log
ACs
- The config.yaml resource file should be loaded only and have ResourceChangeHandler registered
- Should not block the startup process when having the similar config.yaml resource with file path with folder name doesn't match with any registered module.
Acceptance criteria
- is depended upon by
-
MGNLSSO-188 Refresh SSO config when loaded through the YAML bridge
- Closed
1.
|
Implement | Completed | Nguyen Phung Chi | |
2.
|
QA | Completed | Enrique Espana | |
3.
|
Pre-Integration QA | Completed | Evzen Fochr | |
4.
|
Review | Completed | Evzen Fochr |