[MGNLRES-208] Support author vs public resources Created: 31/Aug/15  Updated: 02/Dec/22  Resolved: 02/Dec/22

Status: Closed
Project: Magnolia Resources Module
Component/s: resourceLoaders
Affects Version/s: 2.4.1
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Edgar Vonk Assignee: Sang Ngo Huu
Resolution: Won't Do Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: 0.25d
Original Estimate: Not Specified

Issue Links:
Relates
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)
Date of First Response:
Epic Link: Maintenance of Resources module
Team: Nucleus

 Description   

As reported in SUPPORT-5053 in Magnolia 5.3 we have different JCR-based configurations per Magnolia instance (author vs public). I think this quite a typical use case because often in our projects we have different configurations per Magnolia instance, not all of which we want to explicitly program in Java code in our version handlers.

So therefore I think it would be nice if Magnolia would support 'instance-based configurations' for YAML-based configuration/resources so that when moving all to YAML at some time in the future this is also still possible.


Generated at Mon Feb 12 06:48:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.