- From: Joshua Miller <
>
- To:
- Subject: [chef] Re: Re: search and order of results
- Date: Wed, 26 May 2010 20:34:03 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:message-id :references:to:x-mailer; b=WmjhzVJy5smOqI8kav/k31fALLi03xlN4YAK7RYINL/I22v9GbEigOzULisyf5pFBi dq3vorqNlqhjepnTsdmkvrVqcXuub4DdhImehIdalYRH4ji9ipAYCgWTCnyacoB5IIdK pqYpsWtQi82GSLqZbte9Zb9cPq5zCA/pi40Mg=
I love ridding public transportation as is give me a mental break and go duh ... .sort
template "/etc/perlbal/perlbal.conf" do source "perlbal.conf.erb" mode 0440 owner "root" group "root" variables( :WEBSERVER_ROLE_host => WEBSERVER_ROLE_host.sort, :APACHE_ROLE_host => APACHE_ROLE_host.sort ) backup 1 notifies :restart, resources(:service => "perlbal") end
On May 26, 2010, at 8:14 PM, Mark Imbriaco wrote: On May 26, 2010, at 10:08 PM, Joshua Miller <
">
> wrote: Search order is inconsistent, is there a way to deal with it? I really would not care except every time chef runs it restarts perbal which is a issue.
[snip] search(:node, "role:WEBSERVER_ROLE") do |n| WEBSERVER_ROLE_host << n['ipaddress'] end
[snip] My Template:
CREATE POOL app_pool <% @WEBSERVER_ROLE_host.each do |n| -%> POOL app_pool ADD <%= n %>:80 <% end -%>
You could do something like WEBSERVER_ROLE_host.sort.each in the template to ensure that the array is sorted before you iterate over it.
|
Archive powered by MHonArc 2.6.16.