On Apr 20, 2010, at 3:22 AM, David Schmitt wrote:
On 4/20/2010 11:53 AM, Thomas Bellman wrote:
Luke Kanies wrote:
Because imports are parse-time, not compile-time. That is, they're
evaluated as the file is read, rather than when a given host's
configuration is compiled.
Related: I do find it a bit confusing that you can write imports
anywhere in the manifests, like inside classes or inside if or
case statements, yet they are *always* executed. Would it be
possible to forbid imports at any other place than "top-level"
in a manifest file?
+1, especially if the surrounding scope has no influence (like
namespacing) on the imported file. Which (I think) is the case.
I'd accept that patch.
--
Progress isn't made by early risers. It's made by lazy men trying to
find easier ways to do something. --Robert Heinlein
---------------------------------------------------------------------
Luke Kanies -|- http://puppetlabs.com -|- +1(615)594-8199
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
