On Wednesday, March 20, 2013 7:16:17 AM UTC-7, blalor wrote:
>
>
>
> Isn't puppetd deprecated in favor of "puppet agent"? I
> use --detailed-exitcodes with "puppet apply" and Puppet 3 and it works like
> it says on the box.
>
>
huh. never realized there was such a flag. Thanks for that. but re
On 03/20/2013 03:26 PM, MartinW wrote:
> Thanks for the replies. I may have found why --test isn't giving the
> expected response.
>
> puppetd --version
> 0.25.5
Yea, shame on you.
> :o - I have no choice but to continue using it as well. Will it be
> impossible for me to get this working with s
Thanks for the replies. I may have found why --test isn't giving the
expected response.
puppetd --version
0.25.5
:o - I have no choice but to continue using it as well. Will it be
impossible for me to get this working with such an old version?
--
You received this message because you are subs
Hi,
good find. As far as I've learned, --test implies the "funny exit codes"
option, so you likely want to try "puppet agent --one-time --nodaemonize".
HTH,
Felix
On 03/20/2013 03:00 PM, MartinW wrote:
> I read on the puppet documentation web pages that there is a parameter
> called --detailed-e
On Mar 20, 2013, at 8:00 AM, MartinW wrote:
> I read on the puppet documentation web pages that there is a parameter called
> --detailed-exitcodes which I thought might help but that doesn't work at all:
>
> puppetd --test --detailed-exitcodes --env test
> invalid option: --detailed-exitcodes
>
I am writing a bash script which will run puppet as follows:
puppetd --test --env test
I need my script to be able to tell if puppet ran successfully, I thought I
might be able to do this by checking the exit code ($?) but it seems that
regardless of whether the puppet run succeeds or fails it
