HAProxy configuration is not being updated

[geowa4]

I've spent part of today trying to learn Synapse as I think it could be useful in my infrastructure. I set up a Vagrant box, where I was able to get it to successfully query the AWS API. The issue though was that it never updated the HAProxy configuration. I have committed this learning exercise to GitHub so it can be reproduced easily. I've also copied a portion of the README here for coherence.

Reproduction

vagrant up
vagrant ssh
cd /vagrant
java -jar synapse.jar --config bug.json
# quit
cat /etc/haproxy/haproxy.cfg

Synapse clearly indicates via standard out that it has identified the two EC2 instances.
It does not modify /etc/haproxy/haproxy.cfg as configured though it reports that it has regenerated the config.

synapse.jar was built with the source at e012cd3 in airbnb/synapse.

[Jaykah]

Looks like the issue that I'm also having - check out #94 for details.

[jolynch]

@geowa4 I think you may have run into an issue with the documentation saying options were default to true (do_writes, do_reloads, do_socket) when they were not at the time. On latest master do you still see the issue? Can you paste your config?

I believe I have a fix for MRI installs in #138, but it looks like you're using JRuby?

[geowa4]

@jolynch Since this didn't work for me almost a year ago, I decided to use something else. If I have time, I might verify this is fixed, but, honestly, I can't put this too high up on my priority list.

[jolynch]

OK, I'm going to close the issue since I think the documentation and code have been fixed. If you come across the problem again please let me know.