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
I just discovered a discrepancy between what the compatibility of this cookbook stated in the metadata.rb file and its actual compatibility. metadata.rb states that this cookbook is compatible with chef_version '>= 12.1', but it is actually only compatible with Chef version 12.14 and above because cookbook yum 5.x is only compatible with Chef >= 12.14 (see changelog of yum cookbook).
Either the value of chef_version should be changed to '>= 12.14' or the constraint on the yum cookbook should be changed to '>= 4.2.0'.
For us, changing the constraint on the yum cookbook would be preferable because we are still on Chef 12.7.
The text was updated successfully, but these errors were encountered:
@wndhydrnt Thank you for reporting. As elastic_beats_repo setup core elastic repository, not specifically for beats, it can be used to install any elastic package.
So, I have created another cookbook elastic_repo. It does more or less the same, but provides elastic_repo resource.
I am updating beats cookbooks to use elastic_repo instead.
I just discovered a discrepancy between what the compatibility of this cookbook stated in the metadata.rb file and its actual compatibility.
metadata.rb
states that this cookbook is compatible withchef_version '>= 12.1'
, but it is actually only compatible with Chef version 12.14 and above because cookbookyum
5.x is only compatible with Chef >= 12.14 (see changelog of yum cookbook).Either the value of
chef_version
should be changed to'>= 12.14'
or the constraint on theyum
cookbook should be changed to '>= 4.2.0'.For us, changing the constraint on the
yum
cookbook would be preferable because we are still on Chef 12.7.The text was updated successfully, but these errors were encountered: