----- Original Message ----- > From: "Peter Huene" <[email protected]> > To: "puppet-dev" <[email protected]> > Sent: Wednesday, July 15, 2015 5:18:29 PM > Subject: Re: [Puppet-dev] How do you know what variables are frozen?
> On Wed, Jul 15, 2015 at 8:59 AM, Trevor Vaughan <[email protected]> > wrote: > >> I *think* I've just run into a case where I was trying to run strip! on a >> frozen Facter variable. >> >> 1) How do we know what variables are frozen coming from Facter? >> > > Facter shouldn't be freezing resolved fact values, so is this something > that a custom fact is explicitly doing to the returned value? > > http://ruby-doc.org/core-2.2.2/Object.html#method-i-frozen-3F should work > for checking in an object is frozen, though. > but surely you should just assume you cant change variables especially facts? since that's their intended use, no modifying of variables? Be interesting to hear why a fact is being tripped in a destructive way :) -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev/142575421.181465.1436977300356.JavaMail.zimbra%40devco.net. For more options, visit https://groups.google.com/d/optout.
