On Tue, May 19, 2009 at 07:58, Andrew Shafer wrote:
>
> What version of Puppet are you running?
0.24.4 -- it's the one that's in the Ubuntu Hardy repository. I could
upgrade, but I would prefer to avoid the effort of setting up
appropriate repositories if I can.
> The goal is to be able to set
What version of Puppet are you running?
The goal is to be able to set up prerequisites for suitability during a run
and have it work.
I thought this was working in new versions.
I have a git provider just waiting for a bit of spare time the would require
this type of logic on most systems and if
On Thu, May 14, 2009 at 00:35, Mike Renfro wrote:
> I may be naive here, since I've never written my own types, but I'm
> wondering if a puppet definition for mysql_user would be better than
> writing a native puppet type. Something like:
>
> mysql_user { "u...@localhost": password_hash => "has
On 5/13/2009 4:10 PM, Jeremy Thurgood wrote:
> The problem is that the provider suitability resolution happens before
> any of the ordering. Consider the following simplified class:
>
> class mysql {
> package { "mysql-client": ensure => installed }
> package { "mysql-server": ensure => i
On Wed, May 13, 2009 at 20:59, Evan Hisey wrote:
> You should be able to do this using the the require and before
> metatypes. Have the package{"mysql": before => Exec["mysql-config]}.
> Some thing liek that should get teh ordering correct for you.
The problem is that the provider suitability re
On Wed, May 13, 2009 at 8:19 AM, jerith wrote:
>
> Good day,
>
> Does puppet have a way of setting up provider dependencies before
> setting up the provider itself?
>
> Here's the scenario I'm trying to get working: I have some machines
> that need to be database servers. I also have a mysql type
