Re: [Puppet Users] design advice on coding my first type / provider

2010-12-12 Thread Richard Crowley
2. is going to do unnecessary work (and I'll have to create the user if they don't exist anyway) I've written types that do this with great success. Be careful that performing that repetitive action isn't expensive or otherwise degrading to normal operation. If it creates any kind of race

[Puppet Users] design advice on coding my first type / provider

2010-12-11 Thread Dick Davies
I just wondered if anyone has experience of this kind of problem, and what approaches they've found to work best. I'm writing my first type/provider (on pupet 0.25.x) to automatically setup RabbitMQ. The basic approach I'm taking is to wrap the rabbitmqctl command (which lets you create vhosts,

Re: [Puppet Users] design advice on coding my first type / provider

2010-12-11 Thread Nigel Kersten
Can you follow the path our user providers use and simply provide the internal hash in the manifest? Can you verify that client side? On Sat, Dec 11, 2010 at 6:48 AM, Dick Davies rasput...@hellooperator.net wrote: I just wondered if anyone has experience of this kind of problem, and what

Re: [Puppet Users] design advice on coding my first type / provider

2010-12-11 Thread Dick Davies
That'd essentially be option 1 then. I think it'd be doable (have seen that work well in e.g. camptocamps mysql module) but I'd need to call into Erlang somehow to find the hashed password. In the mysql case, it's just a straight select out of the mysql.user table. One other idea I had was to