search

mesosphere / marathon

Deploy and manage containers (including Docker) on top of Apache Mesos at scale.
https://mesosphere.github.io/marathon/
Apache License 2.0
4.07k stars 845 forks source link

Support yaml as input format in the API #1775

Closed sttts closed 7 years ago

sttts commented 9 years ago

YAML is much easier to write manually than JSON. JSON files get harder to read and maintain the bigger they get. YAML has support for multiline strings, JSON doesn't. App CMD strings with >500 characters are no fun in JSON.

bobrik commented 9 years ago

Also comments, YAML supports comments.

aquamatthias commented 9 years ago

Thought of that as well so often. Really like the idea. :+1:

bsideup commented 9 years ago

:+1:

MikeMichel commented 9 years ago

+1

kolloch commented 9 years ago

Do you think one could simply put a YAML to JSON converter in front of the logic that we have now? All validation errors (beyond YAML syntax errors) would then of course relate to the JSON...

bsideup commented 9 years ago

@kolloch YAML is just an extension to JSON btw :) So Marathon could replace JSON parser with YML and it MUST be backward compatible

MikeMichel commented 9 years ago

sry, could not resist image

pierluigi commented 9 years ago

:laughing:

shtratos commented 9 years ago

+1

aronica commented 8 years ago

It's much easy to use docker compose to express the relationship between two containers than using group in marathon.

j3k0 commented 8 years ago

:+1:

tsaridas commented 8 years ago

+1

charlesmims commented 7 years ago

+1

EMChamp commented 7 years ago

+1, JSON gets horribly complicated to maintain and readability suffers.

meichstedt commented 7 years ago

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-2710. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.