[MAGNOLIA-6165] Simple include mechanism for yaml config files Created: 14/Apr/15 Updated: 12/May/15 Resolved: 06/May/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | configuration |
| Affects Version/s: | None |
| Fix Version/s: | 5.4 |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Until we reach conclusions and good design on how we're going to handle "extends" in the long run for configuration, we can implement a simple include mechanism for yaml files:
|
| Comments |
| Comment by Magnolia International [ 06/May/15 ] |
|
Current implementation supports absolute paths only. See magnolia-configuration/src/test/resources/info/magnolia/config/source/yaml/samples/includes.yaml for examples. |
| Comment by Mikaël Geljić [ 07/May/15 ] |
|
Feature works nicely on technical grounds, but one has to know about some caveats at the moment: a. Includee has to be visible in the same LayeredOrigin instance as the includer
b. Assuming we put includee e.g. inside the apps directory:
That said, there's no real change to be considered in the include mechanism itself, but rather in Origins. Considering all of this, this is now reviewed. |