standalone.conf gets updated every chef-client run, even with no changes to it.

[krnorman]

Every single time chef-client runs (every 30 mins), standalone.conf gets updated, which in turn triggers a restart of the service.

chef-wildfly/resources/wildfly.rb

Lines 141 to 149 in ef3edfd

	wf_props = file 'WildFly - Service Properties' do
	content new_resource.server_properties.join("\n")
	path ::File.join(new_resource.base_dir, new_resource.mode, 'configuration', 'service.properties')
	owner new_resource.service_user
	group new_resource.service_group
	mode '0640'
	action :create
	notifies :restart, "service[#{new_resource.service_name}]", :delayed
	end

I've made a backup of the file then run chef-client, and verified that there is no difference in content (verified by MD5), ownership, or permissions between the old and new versions of the file, so I don't understand why it's getting updated/modified/touched at all. But the wildfly service restart makes this unusable.
Obviously that's not desired behavior, but I don't know if there's something I'm doing I shouldn't be, or if there's something I'm not doing that I should be, or if the recipe is genuinely misbehaving.

I'm calling the default recipe (with attributes to disable the mysql and postgresql recipes) from my downstream recipe, installing wildfly 10.1.0-Final on a Centos 7 node. I'm also including attributes for the standalone.conf parameters:

# => The defaults are adjustable here
default['wildfly']['java_opts']['xmx'] = '2048m'
default['wildfly']['java_opts']['xms'] = '512m'
default['wildfly']['java_opts']['xx_metaspacesize'] = '96m'
default['wildfly']['java_opts']['xx_maxmetaspacesize'] = '256m'
default['wildfly']['java_opts']['preferipv4'] = 'true'
default['wildfly']['java_opts']['headless'] = 'true'

# => Specify other java options in this space-deliniated array.
default['wildfly']['java_opts']['other'] = %w(
  -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.security.egd=file:/dev/../dev/urandom
)