Fixed trailing comma bug
Fixed trailing comma bug

Depending on the options specified, there could be a trailing comma which is invalid JSON and prevented consul from starting. Lame but easy solution was to make a required configuration be the last one and never have a trailing comma and made sure all other configs do end in a comma.
adriagalin/ansible-consul,MrMMorris/ansible-consul,tomjrob/ansible-consul,msabramo/ansible-consul,MrMMorris/ansible-consul,savagegus/ansible-consul,mhamrah/ansible-consul,jonbrandenburg/ansible-consul,jivesoftware/ansible-consul,savagegus/ansible-consul,cloudstrap/ansible-consul,lbaldwin123/ansible-consul,benjaminws/ansible-consul,tomjrob/ansible-consul,tomhite/ansible-role-consul,cloudstrap/ansible-consul,wernerb/ansible-consul-yum,trumant/ansible-consul,trumant/ansible-consul,msabramo/ansible-consul,jivesoftware/ansible-consul,jonbrandenburg/ansible-consul,adriagalin/ansible-consul,robbiet480/ansible-consul,lbaldwin123/ansible-consul,wernerb/ansible-consul-yum,robbiet480/ansible-consul