You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Chef 12 these warnings now show up for the chef-datadog cookbook.
[2015-03-24T15:38:02+00:00] WARN: chef_gem[chef-handler-datadog] chef_gem compile_time installation is deprecated
[2015-03-24T15:38:02+00:00] WARN: chef_gem[chef-handler-datadog] Please set `compile_time false` on the resource to use the new behavior.
[2015-03-24T15:38:02+00:00] WARN: chef_gem[chef-handler-datadog] or set `compile_time true` on the resource if compile_time behavior is required.
As noted by @jtimberman these can be fixed by adding this line to the resource for maximum backward compatibility.
compile_time true if Chef::Resource::ChefGem.instance_methods(false).include?(:compile_time)
Thanks for reporting this. There's been an ongoing thread on the Chef mailing lists on the behavior of compile_time and Chef 12.
Yesterday, a post-mortem was produced: https://gist.github.com/thommay/42b033d2c877e74e6b1a
In Chef 12, the compile_time behavior flag was added, leading to WARN
messages showing up in the Chef Client execution.
Since the current method to invoke a handler is via a recipe, we need to
install the gem during compile time to allow loading the handler to
caputer execution items.
See https://www.chef.io/blog/2015/02/17/chef-12-1-0-chef_gem-resource-warnings/
for more details on the new flag.
Fixes#189
With Chef 12 these warnings now show up for the chef-datadog cookbook.
As noted by @jtimberman these can be fixed by adding this line to the resource for maximum backward compatibility.
See http://jtimberman.housepub.org/blog/2015/03/20/chef-gem-compile-time-compatibility/
The text was updated successfully, but these errors were encountered: