[MAGNOLIA-6076] Make config by file optional Created: 16/Feb/15  Updated: 15/Mar/21  Resolved: 15/Mar/21

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

Type: Improvement Priority: Neutral
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: config
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-6075 Follow java-free module conventions b... Closed
dependency
depends upon MAGNOLIA-6027 IoC: Support multi-binding Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Config by file / code
Story Points: 8

 Description   

Currently, config-by-file is bound to registries via the YamlConfigurationSourceBuilder, which requires each module having a registry to build such source, using sensible default for e.g. root path or file name regex pattern.

In this step, we want to make it optional to have file-observation set up.

This should be a separate optional module in main, using Guice multi-bindings for example, to initialize these default config-sources for all registries currently alive in the system.



 Comments   
Comment by Mikaël Geljić [ 15/Mar/21 ]

Closing as outdated; next iteration might attempt to address this issue with a RegistryBuilder, auto-wired to selected ConfigurationSources.

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