init_defaults doesn't work properly with java opts values about puppet-elasticsearch HOT 10 CLOSED

Interesting issue. can you give me an example value for the ES_JAVA_OPTS?
Will do some investigation on this and add testing.

from puppet-elasticsearch.

I found this discussion from a while back, but I think the solution is valid. http://www.redhat.com/archives/augeas-devel/2008-October/msg00023.html

In a quick test I put single quotes around the <%= value %> in defaults.erb so it looks like this:

<% @init_defaults.sort.map do |key, value| -%>
set <%= key %> '<%= value %>'
<% end -%>

Then, in my init_defaults hash I set
ES_JAVA_OPTS => '"-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=9012 -Dcom.sun.management.jmxremote.ssl=false"' as an example (that's double quotes wrapped in single quotes). The end result is that the set command looks like:
set ES_JAVA_OPTS '"-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=9012 -Dcom.sun.management.jmxremote.ssl=false"'

The double quotes carry through and end up as the following line in /etc/sysconfig/elasticsearch - and works beautifully.
ES_JAVA_OPTS="-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=9012 -Dcom.sun.management.jmxremote.ssl=false"

Would you be interested in a fix like this? It's completely backward compatible as far as I can tell.

from puppet-elasticsearch.

Ahh interesting. Totally didn't expect that.
Assuming it won't cause any issues with other values ( numbers, true/false ) im happy with the fix :-)

from puppet-elasticsearch.

Ok, I'll see if I can write some tests. Thanks for the feedback.

from puppet-elasticsearch.

I made the change. I don't think it will break current tests. I'm struggling to get the tests working on my box so I'm not sure if I'll be able to add new tests.

from puppet-elasticsearch.

What command is needed to execute the tests? Including ENV vars? I think that's my issue.

from puppet-elasticsearch.

Hi,

Commands are in .travis.yml file but might fail in certain scenario's because i messed something up.

bundle install
bundle exec rake spec SPEC_OPTS='--format documentation'

from puppet-elasticsearch.

\o/ Thank you!

from puppet-elasticsearch.

Updated PR #106 with tests to account for this change.

from puppet-elasticsearch.

I'm seeing this with the latest version of the module (from the forge - 0.15.0).
Since we cannot specify ES_HEAP_SIZE anymore with elasticsearch 5, I set ES_JAVA_OPTS but when I try with the space (ES_JAVA_OPTS="-Xms8g -Xmx8g") then augeasproviders_shellvar fails.

When I try with just ES_JAVA_OPTS="-Xmx8g" it works fine.

Anyone aware of a workaround?

from puppet-elasticsearch.