> We should either say we have a data story that revolves around:
> 
> - facts
> - parameterized classes
> - ENCs and systems like Hiera
> 
> these are all hard non magical things, you know where your variables come
> from. You know what they are and what can override them.  Mix in the @facts
> style syntax and this story becomes even clearer.
> 
> If we were to expand this list to include:
> 
>  - magical node variables that can override top scope vars in some cases
> 
> 
> Then it's quite clear to me which is the elephant in the room and shouldnt
> be there.
> 

Whilst I'm not so keen on the @facts syntax I agree with RI. We already
have magic variables (which have changed their magical properties
several times since my involvement with the project) we don't need
anymore magic.

James

-- 
James Turnbull
Puppet Labs
1-503-734-8571
To schedule a meeting with me: http://tungle.me/jamtur01

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-dev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-dev?hl=en.

Reply via email to