[MAGNOLIA-8674] Register definition from un-registered module when loading <module_name>/config.yaml Created: 04/Jan/23  Updated: 18/Feb/23  Resolved: 19/Jan/23

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 6.2.27
Fix Version/s: 6.3.0, 6.2.28

Type: Bug Priority: Neutral
Reporter: Nguyen Phung Chi Assignee: Nguyen Phung Chi
Resolution: Fixed Votes: 1
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 6d 1h Time Spent: 6d 1h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: Text File 6.2_SSO_install_and_startup_error.log    
Issue Links:
dependency
is depended upon by MGNLSSO-188 Refresh SSO config when loaded throug... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-8675 Implement Sub-task Completed Nguyen Phung Chi  
MAGNOLIA-8676 QA Sub-task Completed Enrique Espana  
MAGNOLIA-8677 Pre-Integration QA Sub-task Completed Evzen Fochr  
MAGNOLIA-8678 Review Sub-task Completed Evzen Fochr  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: SSO maintenance
Sprint: AdminX 27
Story Points: 2
Team: AdminX
Work Started:

 Description   

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.
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".

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.

Generated at Mon Feb 12 04:34:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.