[MAGNOLIA-8044] Invert dependency between Registry and Configuration Source Created: 07/Apr/21  Updated: 22/Jun/22  Resolved: 14/May/21

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

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Rabie Hayoun
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLCT-174 Adapt ContentTypeRegistry to the inve... Closed
is cloned by MGNLUI-6666 Adapt UI framework to new Registry an... Closed
is cloned by PSWDMNGR-24 Adapt password manager to registry PoC Closed
Problem/Incident
causes MGNLRESTCL-179 Test failures after bumping to Java 11 Closed
Relates
relates to MAGNOLIA-8073 Merge S3 configuration source and reg... Closed
relation
is related to MAGNOLIA-8481 Review ConfigurationSource / Registry... Selected
Template:
Acceptance criteria:
[X]* registry keeps no resolved configuration state on its own
[X]* configuration source keeps the state of the definitions it discovered
[X]* decoration is either discarded in PoC or (better) resolved/applied in the cfg source
[X]* (optionally) validation can be still applied on registry level
Task DoR:
Empty
Epic Link: SaaS project configuration
Sprint: Cloud Service 5, Cloud Service 6, Cloud Service 7, Cloud Service 8, Cloud Service 9
Story Points: 21

 Description   

,


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