- From: Tollef Fog Heen <
- Subject: [chef-dev] Re: Re: Re: Re: Re: Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes
- Date: Tue, 27 Mar 2012 22:36:53 +0200
]] Joe Williams
Hi Joe, *
> [...] Search is awesome and I want to make good use of it but we
> deploy often enough that it can wait until we ship more code and tell
> chef to update the config. So the end result is a steady state
> run_list that everyone can expect to keep the system in check and
> updated and then when developers do their deploys a single application
> recipe chef-client run with only that recipe in the
It sound to me somewhat like you want profiles where a profile is an
overlay of a node.
This means you can do something like chef-client -n $(hostname -f):app1
to get the overlay for app1, which overrides the run list (and maybe
some other parameters). $(hostname -f):app1 can be edited like a node
object, but is really closer to a role that's applied at runtime rather
than an overlay node. Maybe it should actually be a role, even.
Slightly like a very lightweight per-node set of environments.
Sure, this requires somebody to write other code than what's already on
the table, but I think it's a better model for what you're trying to
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
- [chef-dev] Re: Re: Re: Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes, (continued)
- [chef-dev] Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes, AJ Christensen, 03/26/2012
- [chef-dev] Re: CHEF-2988 allowed_recipes, restricted_recipes, and override_recipes, Bryan McLellan, 03/28/2012
Archive powered by MHonArc 2.6.16.