[MAGNOLIA-8073] Merge S3 configuration source and registry refactoring efforts Created: 22/Apr/21  Updated: 09/Nov/21  Resolved: 09/Nov/21

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

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Rishab Dhar
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-8044 Invert dependency between Registry an... Closed
relates to MAGNOLIA-8045 PoC: REST-based configuration source Closed
relates to MGNLCT-174 Adapt ContentTypeRegistry to the inve... Closed
relates to MAGNOLIA-8060 Resolve definitions from light module... Closed
Template:
Acceptance criteria:
[X]* config source still fetches definitions and decorators from S3
[X]* the state of the resolved definitions is kept in the configuration source
[X]* the experimental config source introduced by magnolia-8044 is either retired or merged with the current YAML configuration source (at least we don't have any un-usable or redundant config sources left).
Task DoR:
Empty
Epic Link: SaaS project configuration

 Description   

Use the S3 configuration source prototype results and apply the registry vs config source refactoring (see AC).



 Comments   
Comment by Aleksandr Pchelintcev [ 09/Nov/21 ]

The AC of this issue has been fulfilled by the linked efforts/tickets.

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