Issue #2557 has been updated by Luke Kanies. Category set to executables Status changed from Unreviewed to Needs design decision
I'm not even sure this should work -- '-e' is meant to be used without an actual manifest. That being said, I don't see a specific reason why it shouldn't be allowed. But even then... I actually think I would normally expect the -e to run first. What do others think? ---------------------------------------- Bug #2557: -e with puppet appears to execute first http://projects.reductivelabs.com/issues/2557 Author: Larry Ludwig Status: Needs design decision Priority: Normal Assigned to: Category: executables Target version: Complexity: Unknown Affected version: 0.24.8 Keywords: In the code example <pre> $myvar='foo' class test { alert ("myvar: ${myvar}") } include test </pre> Yields the result: lludwig$ puppet test.pp alert: Scope(Class[test]): myvar: foo </pre> Yet, if your remove the 'include test' and execute it via the command line yields a different result. <pre> lludwig$ puppet test.pp -e 'include test' alert: Scope(Class[test]): myvar: </pre> It appears from other tests that the 'include test' via the command line is executed first. Shouldn't load all .pp files and execute last? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
