I can run $ lsb-release -a on the servers in question and it returns the
information I expect. When I use the @lsbdistdescription the local puppet
daemon does not acknowledge the field. That line simply gets the
architecture. With the @ there is nothing to report when I look in
foreman, when
On 04/22/2014 04:36 PM, Sans wrote:
> You sure it's just a "recommendation"? IIRC, it doesn't work with Ruby
> v1.9.x.
> But that's definitely not the actual problem here though.
That's right.
The @ is just to safeguard against an issue where variable names clash
with method names from the ruby k
On Tuesday, April 22, 2014 2:35:05 PM UTC+1, jcbollinger wrote:
>
>
>
> That is the current recommendation, but it is not a requirement. Bare
> variable names work, too.
>
You sure it's just a "recommendation"? IIRC, it doesn't work with Ruby
v1.9.x.
But that's definitely not the actual pro
On Monday, April 21, 2014 4:45:09 PM UTC-5, zjhe...@gmail.com wrote:
>
> Having an odd issue with the facts inside an ERB template. I'm using the
> facts to build a somewhat dynamic MOTD. I made some changes to init.pp for
> the module and deployed to my Dev environment and it started breakin