Do you ever search for [role] or [recipe] instead of [roles] and [recipes]?
Why? Would you be traumatized if these went away (because they’re
confusing) in Chef 11 and you had to look through the nodes run_list?
Do you use node[:recipes] and run_state[:seen_recipes] in a cookbooks to
determine if a recipe is in the expanded run list but hasn’t been seen yet?
Would you hold it against me if node[:recipes] contained the recipes that
had been seen/loaded so far (and the final list of all recipes at the end
of the run, including ones from include_recipe), instead of the expanded
run_list?
On Wed, Dec 5, 2012 at 12:51 PM, Bryan McLellan btm@loftninjas.org wrote:
Do you use node[:recipes] and run_state[:seen_recipes] in a cookbooks to
determine if a recipe is in the expanded run list but hasn't been seen yet?
Would you hold it against me if node[:recipes] contained the recipes that
had been seen/loaded so far (and the final list of all recipes at the end
of the run, including ones from include_recipe), instead of the expanded
run_list?
I'm going to presume that means you'd like to see that proposal happen,
rather than you are really^10 going to be grumpy at me.
Indeed. We would love to see this included. It is particularly important
when we are auditing which cookbooks are on which node and what not. In
particular
what we have in a recipe, (derived from the knife audit plugin) is as
follows. It would be nice to eliminate the need for this.
ruby_block "get_seen_recipes" do
block do
node.override["knife_audit"]["seen_recipes"] =
node.run_state[:seen_recipes]
end
action :create
end
We search for "role" only because I read somewhere that searching against
"roles" is much more expensive. But it has bitten us before.
While I wouldn't mind if "role" went away, I'd want to know that the
performance of searching for "roles" wasn't going to be awful.
Julian
On Tue, Dec 4, 2012 at 8:51 PM, Bryan McLellan btm@loftninjas.org wrote:
Do you ever search for [role] or [recipe] instead of [roles] and
[recipes]? Why? Would you be traumatized if these went away (because
they're confusing) in Chef 11 and you had to look through the nodes
run_list?
Do you use node[:recipes] and run_state[:seen_recipes] in a cookbooks to
determine if a recipe is in the expanded run list but hasn't been seen yet?
Would you hold it against me if node[:recipes] contained the recipes that
had been seen/loaded so far (and the final list of all recipes at the end
of the run, including ones from include_recipe), instead of the expanded
run_list?
We search for "role" only because I read somewhere that searching against
"roles" is much more expensive. But it has bitten us before.
While I wouldn't mind if "role" went away, I'd want to know that the
performance of searching for "roles" wasn't going to be awful.
Julian
On Tue, Dec 4, 2012 at 8:51 PM, Bryan McLellan btm@loftninjas.org wrote:
Do you ever search for [role] or [recipe] instead of [roles] and
[recipes]? Why? Would you be traumatized if these went away (because
they're confusing) in Chef 11 and you had to look through the nodes
run_list?
Do you use node[:recipes] and run_state[:seen_recipes] in a cookbooks to
determine if a recipe is in the expanded run list but hasn't been seen
yet? Would you hold it against me if node[:recipes] contained the recipes
that had been seen/loaded so far (and
the final list of all recipes at the end of the run, including ones from
include_recipe), instead of the expanded run_list?
