Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating to yaml.v3 #106

Merged
merged 1 commit into from
Nov 15, 2019
Merged

Migrating to yaml.v3 #106

merged 1 commit into from
Nov 15, 2019

Conversation

laszlocph
Copy link
Member

@laszlocph laszlocph commented Nov 15, 2019

#103 another attempt to fix.

The monkeypatched yaml.v2 was not working properly. Trying to fix it the right way ™️

@laszlocph laszlocph force-pushed the yaml-v3 branch 2 times, most recently from 32b713d to f32f77b Compare November 15, 2019 09:16
@@ -54,10 +54,6 @@ volumes:
- /var/lib/mysql
- /opt/data:/var/lib/mysql
- /etc/configs:/etc/configs/:ro
ulimits:
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dropped support for ulimits, man gotta focus..

@@ -44,7 +44,7 @@ func TestBoolTrue(t *testing.T) {
})

g.It("should throw error when invalid", func() {
in := []byte("{ }") // string value should fail parse
in := []byte("abc") // string value should fail parse
Copy link
Member Author

@laszlocph laszlocph Nov 15, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yaml.v3 interprets {} as a map

@laszlocph laszlocph merged commit e2801e8 into master Nov 15, 2019
@laszlocph laszlocph deleted the yaml-v3 branch November 15, 2019 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant