On Tue, Feb 8, 2011 at 10:38 PM, chakra wrote:
> Hello,
>
> I tried using config_version with my simple shell script which returns
> my SVN revision number. but puppet doesn't seem to be applying the
> config version in the logs.
>
> More Details
> Puppet Master/Client Version: 2.6.4
> config_ver
Hi Guys,
Anybody got config_version working ?
Cheers,
Chakra
On Wed, Feb 9, 2011 at 12:08 PM, chakra wrote:
> Hello,
>
> I tried using config_version with my simple shell script which returns
> my SVN revision number. but puppet doesn't seem to be applying the
> config version in the logs.
>
Hello,
I tried using config_version with my simple shell script which returns
my SVN revision number. but puppet doesn't seem to be applying the
config version in the logs.
More Details
Puppet Master/Client Version: 2.6.4
config_version = /usr/loca/bin/get_revision ( this line is placed
under [m
Hi All
For those that use, or want to use config_version, you might want to watch
http://projects.puppetlabs.com/issues/3692
My debugging (with webrick) shows that the puppet server only executes the
script defined in config_version at daemon startup, no matter how many
clients connect.
John
--
I am on version 0.25.4 of puppet and facter 1.5.2, I don't see the fact nor
the version anywhere in the clients catalog (on the client). I know its
available via reports to send to a host somewhere but I am curious if this
data is available on the client itself.
# facter config_version
#
On Tue
AFAIK, its also a fact, which makes it really easy to report with Foreman.
Ohad
On Tue, Dec 7, 2010 at 8:41 PM, Christopher Johnston wrote:
> So I got this working by calling an external script to run a git rev-parse
> and to dump the current revision, looks like it works. But I think what is
>
On Tue, Dec 7, 2010 at 10:48 AM, Dan Bode wrote:
>
>
> On Tue, Dec 7, 2010 at 10:41 AM, Christopher Johnston
> wrote:
>>
>> So I got this working by calling an external script to run a git rev-parse
>> and to dump the current revision, looks like it works. But I think what is
>> of value here is
On Tue, Dec 7, 2010 at 10:41 AM, Christopher Johnston wrote:
> So I got this working by calling an external script to run a git rev-parse
> and to dump the current revision, looks like it works. But I think what is
> of value here is to be able to see what the individual hosts current
> config_ve
So I got this working by calling an external script to run a git rev-parse
and to dump the current revision, looks like it works. But I think what is
of value here is to be able to see what the individual hosts current
config_version is currently at since its last run. This is useful to
determine
Am 16.03.2010 17:16, schrieb Daniel Kerwin:
> is it possible to add a system variable like config_version to a template?
I don't understand your question? What do you mean with "system variable"?
Facts? Manifest variables?
Do you want just to *use* variables in templates? Do you want to set them
Hi list,
is it possible to add a system variable like config_version to a template?
--
Cheers,
Daniel
--
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 th
11 matches
Mail list logo