bflad / chef-java-management Goto Github PK

Only stub test file currently.

When adding a key to the truststore, the resource skips the action if the key already exists but still sends a updated message, causing notifies to fire.

http://stackoverflow.com/questions/21176576/how-to-i-get-a-chef-custom-lwrp-to-implement-notifies-and-not-if

Recipe truststore fails when a JRE is installed. Chef client ends with the following error:

==> default: [2014-10-10T23:07:49+00:00] ERROR: file[/usr/java/default/jre/lib/security/truststore-my_root.pem] (java-management::truststore line 32) had an error: Chef::Exceptions::EnclosingDirectoryDoesNotExist: Parent directory /usr/java/default/jre/lib/security does not exist.

This is due to the following assignment in the recipe:

certificate_file = "#{node['java']['java_home']}/jre/lib/security/truststore-#{certalias}.pem"

certificate_file is a valid path when a JDK is installed. In case of a JRE installation, this path should be:

certificate_file = "#{node['java']['java_home']}/lib/security/truststore-#{certalias}.pem"

The default value of the keystore attribute in the truststore LWRP provider should also be set accordingly.

A possible fix could be to allow setting this path as a cookbook attribute.

Thank you for your support.

https://github.com/sethvargo/chefspec#packaging-custom-matchers