Addresses issue 99 where Juju has a problem with strings starting with zero #104

Merged
merged 3 commits into from Feb 6, 2016

Conversation

Projects
None yet
2 participants
Contributor

mbruzek commented Feb 6, 2016

This pull forces all strings to use quotes so Juju does not try to read the yaml string 01182252 as an int.

Adding configuration and tests so this does not revert in the future.

I also had to fix a hash on metadata.yaml in the tests, don't know what that was about other than the test was failing when I found it.

Owner

marcoceppi commented Feb 6, 2016

Lgtm, the hash is the has of the file. So this needs to be updated since content has changed.

Did not QA, will wait for travis

Owner

marcoceppi commented Feb 6, 2016

Fixes #99 ⛵️

Contributor

mbruzek commented Feb 6, 2016

@marcoceppi the hash was for metadata.yaml not config.yaml (which changed in this PR), so I don't know why the hash value for metadata changed.

@marcoceppi marcoceppi added this to the PATCH milestone Feb 6, 2016

marcoceppi added a commit that referenced this pull request Feb 6, 2016

Merge pull request #104 from mbruzek/issue-99
Addresses issue 99 where Juju has a problem with unquoted strings, with proceeding 0 and all numbers

@marcoceppi marcoceppi merged commit 45bfaeb into juju:master Feb 6, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
Owner

marcoceppi commented Feb 6, 2016

@mbruzek can you open a bug against the go-yaml library Juju uses to fix this at its source?

Contributor

mbruzek commented Feb 9, 2016

@marcoceppi go-yaml/yaml#157

@srbaker This charm-tools patch works around your problem, but I have traced the root back to the go-yaml implementation and opened an issue go-yaml/yaml#157

@marcoceppi marcoceppi modified the milestones: 2.0, PATCH Mar 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment