[MAGNOLIA-7186] YamlConfigurationSource wrongly resolves exported YAML app config Created: 25/Oct/17  Updated: 19/Aug/21  Resolved: 19/Aug/21

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

Type: Bug Priority: Neutral
Reporter: Viet Nguyen Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: light-development, y2k
Remaining Estimate: 0d
Time Spent: 1h
Original Estimate: 1h

Attachments: XML File config.modules.tours.apps.destinations.xml     Text File log.txt    
Issue Links:
causality
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

YamlConfigurationSource wrongly resolves exported YAML app config, reference to log.txt for an example.
Steps to reproduce:
1. import destination app from XML file config.modules.tours.apps.destinations.xml to modules > tours > apps
2. test it as it's working correctly
3. export 'that' configuration into YAML
4. remove JCR configuration, rename exported YAML file to destinations.yaml and put it to lightdev module under apps folder
5. open the app and see the issue
Work around:
1. remove first line app name ('destinations' in this case)
2. convert all 'extends' property to use our YAML 'inherit' mechanism
Expected result:
Work seamlessly w/o any modification or provide correct message to end user to fix the configuration.
Suggestion:
Upgrade YamlConfigurationSource.


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