On 06/06/2014 02:07 PM, Sans wrote: > > I think, the problem is coming from the @namebit. Is it right way of > doing it?
@name is indeed the issue - it is bound to a foreign value in this scope. > if I do the same thing in a ruby console, replacing @name with a 'key', > I get exactly what I expect. Any pointer?? Again - my proposal is to strive for a create_resources() based solution without *any* need to resort to templating. >From the data you supplied, there is just no reason for neither invoking to_s nor chomp on your hash values. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5391B39A.4040703%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
