Hi,
When using stored configs with exported resources, I'm getting an odd sort
order for arrays. For example, I have the following resource exported by
all nodes ;
@@sshkey { "${::fqdn}_dsa":
host_aliases => ["$::fqdn","$::hostname","$::hostip"],
type => dsa,
key => $::sshd
FYI
I had this same problem after an upgrade from 2.7.9 to 2.7.10. I'm running
a CentOS 5.7 OpenVZ VPS & don't have access to update the kernel ;
# uname -r
2.6.18-274.7.1.el5.028stab095.1
# facter puppetversion rubyversion virtual
puppetversion => 2.7.10
rubyversio
Hi,
Is it possible to use facts from external nodes via stored configs, based
on a filter such as class? To illustrate, I provide the following use case ;
class nagios::nrpe {
# No such resource "ip". I'd like to use "ip" fact of any node that is
assigned to class "nagios::server"
$nagios_se
On 4 January 2012 07:33, bel wrote:
> I'd reverse my stages if I were you. Seems like that will fix it.
>
> On Dec 27 2011, 11:02 am, Jure Pečar wrote:
> > On Tue, 27 Dec 2011 04:32:03 -0800 (PST)
> >
> > bel wrote:
> > > You could use stages as described in documentation:
> >
> > >http://forge
Hi,
I'm having some trouble using a template to construct URIs in a target
file. How can I prevent the puppet templating engine from trying to
interpret the URIs?
For example, I've got the following class ;
class ldap::config {
$ldap_sizelimit = extlookup("ldap_sizelimit", "500")
$ldap_timel
Scrap that. I'm an idiot.
On 24 March 2014 10:29, Grant Byers wrote:
> Hi,
>
> I'm having some trouble using a template to construct URIs in a target
> file. How can I prevent the puppet templating engine from trying to
> interpret the URIs?
>
> For exampl
