On Sun, Sep 19, 2010 at 2:52 PM, Luke Kanies <l...@puppetlabs.com> wrote: > On Sep 20, 2010, at 1:47 AM, Robin Bowes wrote: > >> On 19/09/10 19:59, Peter Meier wrote: >>>> Would it be possible to make puppet throw an error when this happens? >>> >>> I don't think this is a good idea. I'm using this a lot to tweak what >>> parts of manifests are applied. >> >> That doesn't mean it's a good thing! :) >> >> I'd really like to be able to sanity check my manifests. As it is, >> slight typos can go un-detected, eg. $option vs. $optoin. >> >> Could it at least be made an option? Like a "strict" mode? > > I'm comfortable with a strict mode, but what else would go into that mode? > I'm hesitant to add a mode like this unless it really is a mode and not just > another in the huge list of options.
Maybe we add this too ? http://projects.puppetlabs.com/issues/3933 "Option to make Puppet fail as soon as a resource fails." How would we deal with facts that either return a value or nil and you test for them in your manifests like: if $foobar { } Is the right answer here to instead have a more sophisticated linter that can alert you about such things and that you set up as a precommit hook in your version control system? -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-...@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.
