Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2012-01-30 Thread Felix Frank
On 01/28/2012 12:17 AM, jblaine wrote: Trashing the entire defined resource idea 30 mins ago, and simply trying: But why? class ldapclient::config { case $sys_sshortai { 'RH6': { file { '/etc/openldap/ldap.conf': mode = '444',

Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2012-01-30 Thread jblaine
On Monday, January 30, 2012 4:41:40 AM UTC-5, Felix.Frank wrote: On 01/28/2012 12:17 AM, jblaine wrote: Trashing the entire defined resource idea 30 mins ago, and simply trying: But why? Felix, thanks for the reply. I was just trying stuff out while waiting to see what fleshed out here

Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2012-01-30 Thread Felix Frank
On 01/30/2012 03:50 PM, jblaine wrote: So there's nothing I can refer to inside a basic file resource declaration which refers to the file resource title. That's what I wanted to know (assuming I understand everyone correctly). That's correct, yes. -- You received this message because you

Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2012-01-27 Thread jblaine
Thread back from the dead 5 months later :) Nan, using your code example, I get this with PE 2.0.1: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not match ${ldapclient::params::fileroot}/${name}, at /etc/puppetlabs/puppet/modules/ldapclient/manifests/config.pp:3

Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2012-01-27 Thread Nan Liu
I think you are missing double quotes around: ${ldapclient::params::fileroot}/${name} Sent from my iPhone On Jan 27, 2012, at 17:35, jblaine cjbla...@gmail.com wrote: Thread back from the dead 5 months later :) Nan, using your code example, I get this with PE 2.0.1: err: Could not retrieve

Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2012-01-27 Thread jblaine
Indeed. Trashing the entire defined resource idea 30 mins ago, and simply trying: class ldapclient::config { case $sys_sshortai { 'RH6': { file { '/etc/openldap/ldap.conf': mode = '444', source =

Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2012-01-27 Thread Denmat
The errors are good at locating the source of your issues: err: /Stage[main]/Ldapclient::Config/File[/etc/nslcd.conf]: Could not evaluate: Could not retrieve information from environment production source(s) puppet:///modules/ldapclient/files/RH6/ldapclient::config at

Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2012-01-27 Thread Gary Larizza
On Fri, Jan 27, 2012 at 3:17 PM, jblaine cjbla...@gmail.com wrote: Indeed. Trashing the entire defined resource idea 30 mins ago, and simply trying: class ldapclient::config { case $sys_sshortai { 'RH6': { file { '/etc/openldap/ldap.conf': mode =

Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2012-01-27 Thread jblaine
Den and Gary, thanks for the replies. I am trying to re-use the title (as I understand it). Can I not do that? Do I have to type the name of the file as the title and also at the end of my source = ${ldapclient::params::fileroot}/..., ? Gary, I've removed '/files' as part of

Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2011-08-25 Thread jblaine
On Wednesday, August 24, 2011 6:38:21 PM UTC-4, Nan Liu wrote: On Wed, Aug 24, 2011 at 2:23 PM, jblaine cjbl...@gmail.com wrote: 2.7.3 The heck? ${path} is expanding to the shell environment PATH when I reference it as a variable in my file resource. Isn't this supposed to be the

Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2011-08-25 Thread Stefan Schulte
On Thu, Aug 25, 2011 at 07:44:46AM -0700, jblaine wrote: On Wednesday, August 24, 2011 6:38:21 PM UTC-4, Nan Liu wrote: On Wed, Aug 24, 2011 at 2:23 PM, jblaine cjbl...@gmail.com wrote: 2.7.3 The heck? ${path} is expanding to the shell environment PATH when I reference it as a

[Puppet Users] Can't use ${path} in file resource as its namevar?

2011-08-24 Thread jblaine
2.7.3 The heck? ${path} is expanding to the shell environment PATH when I reference it as a variable in my file resource. Isn't this supposed to be the namevar for file resources? err: /Stage[main]/Ldapclient::Config/File[/etc/ldap.conf]: Could not evaluate: Could not retrieve information

Re: [Puppet Users] Can't use ${path} in file resource as its namevar?

2011-08-24 Thread Stefan Schulte
On Wed, Aug 24, 2011 at 02:23:49PM -0700, jblaine wrote: 2.7.3 The heck? ${path} is expanding to the shell environment PATH when I reference it as a variable FWIW: It doesnt reference the environment variable directly. It references the fact path which in turn is the path environment