[MAGNOLIA-6386] App definitions downloaded as yaml result in incorrect yaml definition Created: 07/Sep/15  Updated: 08/Apr/20  Resolved: 06/Oct/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.4.2
Fix Version/s: 5.4.3

Type: Bug Priority: Neutral
Reporter: Jordie Diepeveen Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: 0d
Time Spent: 2.5d
Original Estimate: Not Specified

Attachments: File config.modules.site-app.apps.site.yaml    
Issue Links:
Relates
relates to MAGNOLIA-6364 Map2Bean doesn't fail with wrong gene... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Basel 13
Story Points: 3

 Description   

Using the download as yaml functionality in AdminCentral for a App definition will result in an incorrect, not working yaml file.

Item like:
availability:
roles:

  • superuser

it exported as
roles:

  • superuser: superuser

and will result in cannot cast map to string exceptions.



 Comments   
Comment by Christoph Meier [ 08/Sep/15 ]

Once the (erroneous!) YAML is created, then it looks like Map2BeanTransformer is "reacting wrong", therefore probly. related to MAGNOLIA-6364.

Comment by Ilgun Ilgun [ 05/Oct/15 ]

Found an issue with exported yaml.

when(user).exportsSiteApp();

then(exportedYaml).hasLineWith(

  • - permissions:
    roles:
    superuser: superuser
    );

I believe "- - permissions:" is not correct, hence i am reopening the ticket.
On the other hand, now yaml document has superuser:superuser so initial issue seemed to be fixed.

Comment by Michiel Meeuwissen [ 09/Aug/16 ]

How about https://jira.magnolia-cms.com/browse/MAGNOLIA-6449?

Comment by Richard Gange [ 08/Apr/20 ]

mihxil sorry for the late response. Yes, this is for sure a problem that needs to be addressed soon. I will try and prioritize it. 

Cheers
Rich

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