The only potential solution I see right now is to put the require in a
define (which i have) that will do a require check on the class. I
would expect this would add some extensive overhead on ever package run.
Sent from my iPhone
On Mar 17, 2010, at 9:09 PM, Ashley Penney <apen...@gmail.com> wrote:
Put in a feature question for global dependencies like I hassle
people about from time to time! We really do need them for setting
some site specific stuff.
On Wed, Mar 17, 2010 at 7:35 PM, Christopher Johnston <chjoh...@gmail.com
> wrote:
I guess my only gripe here is I have about 2 dozen modules most of
install some form of a pkg from yum. So they all have a direct
dependency on my yum module to do the right thing. I would hate to
have to put a require in every single instance that I call the
method to install a pkg. Any ideas on on how to simplify this to
ensure yum is the very first thing that gets configured on my system?
require => [ Class["yum"],
On Tue, Mar 9, 2010 at 5:51 PM, Patrick <kc7...@gmail.com> wrote:
On Mar 9, 2010, at 5:26 AM, Christopher Johnston wrote:
> For example I have a yum module that sets yum configs up, but
obviously I have other modules that depend on the installation of
that yum module in order to use it to install rpms.
I do the same thing with apt. To solve this, I set the files that
need to be set at the global dependency for all packages. Here's an
example.
Package { require => Exec["post-proxy-update"] }
file { "/etc/apt/apt.conf.d/01proxy":
owner => root,
group => root,
mode => 644,
source => "puppet:///aptcacher-client/01proxy",
}
exec { "/usr/bin/apt-get update":
alias => "post-proxy-update",
subscribe => [ File["/etc/apt/apt.conf.d/01proxy"], File["/
etc/apt/sources.list.d/simba.list"] ],
require => [ File["/etc/apt/apt.conf.d/01proxy"], File["/
etc/apt/sources.list.d/simba.list"] ],
refreshonly => true,
}
file { "/etc/apt/sources.list.d/simba.list":
owner => root,
group => root,
mode => 644,
source => "puppet:///local-apt/simba.list",
}
--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com
.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
.
--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com
.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
.
--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com
.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
.
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
