[MAGNOLIA-6106] The yaml configuration source is decoupled from accessing the file system so that the yaml file can be provided from different sources. Created: 05/Mar/15  Updated: 15/Sep/15  Resolved: 18/Mar/15

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

Type: Task Priority: Neutral
Reporter: Michael Mühlebach Assignee: Michael Mühlebach
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-6266 Rename Origin and ResourcePath interf... Closed
causality
is causing MAGNOLIA-6255 Resource loader fails at startup when... Closed
dependency
relation
is related to MAGNOLIA-6214 FreeMarker template scripts should be... Closed
supersession
supersedes MAGNOLIA-6103 Allow for loading configuration files... Closed
is superseded by MAGNOLIA-6128 Introduce uniform resource loading API Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-6113 Rename Layer to Loader Sub-task Closed Michael Mühlebach  
MAGNOLIA-6114 Move DirectoryWatcher code to Filesys... Sub-task Closed Mikaël Geljić  
MAGNOLIA-6115 Introduce pattern in class path origi... Sub-task Closed Michael Mühlebach  
MAGNOLIA-6116 Add register function for resource ob... Sub-task Closed Michael Mühlebach  
MAGNOLIA-6117 Implement classpath origin Sub-task Closed Michael Mühlebach  
MAGNOLIA-6118 Implement filesystem origin Sub-task Closed Mikaël Geljić  
MAGNOLIA-6119 Implement jcr origin Sub-task Closed Aleksandr Pchelintcev  
MAGNOLIA-6122 Integrate FileResourceLoader into Yam... Sub-task Closed Mikaël Geljić  
MAGNOLIA-6125 Extract FileResourceLoader and relate... Sub-task Closed Mikaël Geljić  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Sprint: 5.4 Sprint 1

 Description   

This story is meant as preparation for the merge of configuration origins and resources and to deliver the full experience of cascade loading for the alpha version.

Criterias

  • So the configuration source should be refactored in a way that it should be able to load the yaml file from resources in the future.
  • There should be three different origins the yaml file can be provided: JCR, Filesystem or Classpath but can be accessed in the config source over a common file loader.
  • The order for the lookup should be
    1. JCR
    2. Filesystem
    3. Classpath
  • The file loader has the functionality to observe for changes in the origins.

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