YAML parsing issues about amazon-ecs-cli

[uttarasridhar]

Migrated to libcompose which uses cloudfoundry-incubator/candiedyaml parser for marshalling and unmarshalling YAML.
This issue was fixed in #121 and released in v0.4.0.

[jpetazzo]

Note: I talked about this today with @uttarasridhar; and if I remember well, she mentioned a potential licensing issue with gopkg.in/yaml.v2. To be continued!

[errordeveloper]

This parser is just complete non-sense, I know YAML has pretty complex syntax, but most features are in use widely.

[jdamick]

+1 indentation issues in port example bit me too..

[kapilt]

re gopkg.in/yaml.v2 license, its lpgl with an additional static linking clause such that a static binary does not run afoul of license conveyance issues.

[kapilt]

ibm and pivotal have been working on this as an apache2 licensed replacement. https://github.com/cloudfoundry-incubator/candiedyaml

[errordeveloper]

@kapilt +1

[errordeveloper]

Any takers? ...sounds like swapping the parser shouldn't be too hard, right?

[rprieto]

Swapping parsers sounds great. In the meantime, maybe the ecs-cli docs should state the limitations of the current parser, i.e. that it might not support existing docker-compose.yml files out-of-the-box, and list of gotchas like inline arrays.

[sporokh]

still not fixed?

[jesucarr]

@sporokh I just run into this issue, so no, still not fixed :(

[sporokh]

@jesucarr Thanks for info. Don't know why AWS takes it so long.

[errordeveloper]

Excellent!

On Fri, 8 Jul 2016, 23:11 uttarasridhar, [email protected] wrote:

Closed #13 #13.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#13 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAPWSx1ZWZ7pSHbVFtZvOopAXan96Wsaks5qTssNgaJpZM4GLvUw
.