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
It's there! But looks like the library helper isn't getting the merged attribute from all compile phases, just the one before the initial include_recipe.
I can use node.normal instead of node.default and it works (unfortunately after the second chef run only), but this isn't really optimal. I usually avoid using node.normal since it's usually not coded in recipes and can be a pain.
Expected Result:
Would be great to have the cookbook read the whitelist attribute from all merged attributes from the compile phase, regardless where it was called.
The text was updated successfully, but these errors were encountered:
Cookbook version
5.1.2
Chef-client version
12.20.3
Platform Details
Running on AWS.
Scenario:
Se whitelist items in multiple wrapper cookbooks
Steps to Reproduce:
I'm trying to setup a "base" wrapper cookbook that implements common commands across all servers. For example:
And then, on a separate cookbook, include a custom command only for some servers that use the recipe. For example:
From my knowledge, both attributes are to be merged on the chef compile phase, then used to modify configuration on
/etc/chef/push-jobs-client.rb
.But only the first entry, from the "base" cookbook, is working :(
I double-checked the attribute merging:
It's there! But looks like the library helper isn't getting the merged attribute from all compile phases, just the one before the initial
include_recipe
.I can use
node.normal
instead ofnode.default
and it works (unfortunately after the second chef run only), but this isn't really optimal. I usually avoid usingnode.normal
since it's usually not coded in recipes and can be a pain.Expected Result:
Would be great to have the cookbook read the whitelist attribute from all merged attributes from the compile phase, regardless where it was called.
The text was updated successfully, but these errors were encountered: