Min/Max Pool size modified on every Puppet run adding "" around the values about puppet-wildfly HOT 7 CLOSED

If you use 10 and 60 instead of '10' and '60', you'll probably won't have this problem.

This line is problem the source of this issue: https://github.com/biemond/biemond-wildfly/blob/master/lib/puppet/type/wildfly_resource.rb#L51

I'll change this to should.map(&:to_s).sort == is.map(&:to_s).sort in order to force string to string comparison, do some tests and submit a PR.

And thank you for all the issues you're reporting. Don't hesitate to contact me if you're in trouble.

from puppet-wildfly.

I just tested and using 10 and 60 instead of '10' and '60' and I still see the issue.

from puppet-wildfly.

I wasn't able to reproduce. Are you using wildfly 9?

from puppet-wildfly.

Yes 9.0.0 final.

from puppet-wildfly.

I can look at sanitizing and publishing my vagrant environment if it would help

from puppet-wildfly.

No need. I tested with Wildfly 9 and was able to reproduce the issue.

As a matter of fact, I did a bad reading of your puppet apply output. Wildfly HTTP API is the one who is returning integers instead of strings. =/

I tested with the change proposed in my first comment and it's working on both versions. I'll submit a PR, but be aware that version 0.4.0 introduces some breaking changes (check CHANGELOG.md for more info).

from puppet-wildfly.

pulled down the 3.7 tag and I can double confirm that its working for me also...thanks for the quick fix!

from puppet-wildfly.