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.