A clarification: "whatever kicks Puppet has to run as root as well" could be
something that doesn't run as root but does have sudo permissions!
-- O
On Apr 6, 2013, at 12:23 PM, Owen Smith wrote:
> Greetings,
>
> We are using Puppet to deploy application packages,
Greetings,
We are using Puppet to deploy application packages, so it can indeed be done.
However, you need to do some work around Puppet to enable the use cases you've
mentioned:
* Something builds the package
* Something publishes the package to the yum repo
* Something kicks Puppet on the nod
Agreed on keeping auth and auth separately pluggable concerns. RADIUS and LDAP
are also what I would like for authentication. We'd probably be OK with even an
internal authorization system, since that's what our other management apps use.
-- O
On Mar 2, 2011, at 5:01 PM, Frank Sweetser wrote:
On Nov 18, 1:56 am, Ian Ward Comfort wrote:
> On 18 Nov 2010, at 1:06 AM, Owen Smith wrote:
> >
> > class testa {
> > notify {
> > "note_testa": message => "Test A!";
> > "note2_testa": message => "
Greetings all,
I'm running into an interesting problem that I'm hoping someone out
there knows more about than I.
Consider the following code:
class testa {
notify {
"note_testa": message => "Test A!";
"note2_testa": message => "Test A take 2!"
}
}
class testb {
notify {
