On Tue, Sep 18, 2012 at 3:09 PM, Aaron Grewell <[email protected]> wrote: > On Tue, Sep 18, 2012 at 2:44 PM, Daniel Pittman <[email protected]> wrote: >> On Tue, Sep 18, 2012 at 2:25 PM, Aaron Grewell <[email protected]> >> wrote: > >> Doesn't it close that gap up? >> >> Now, instead of passing 'undef' to a define meaning "use the default >> in the code", it means "use undef" - just like it does when you set >> defaults as you described. >> > > Let me see if I understand. Given this example: > > __________________ > service { httpd: ensure => undef } > > define webserver ( $ensure=stopped ) { > service { httpd: ensure => $ensure } > } > > webserver { ws_foo: ensure => undef } > __________________ > > The old behavior would mean that the bare service resource would not > affect httpd's status, whereas the define would stop the service by > using the default value. The new behavior would mean that the two > would behave identically. Does that sound right?
Yes, that is correct. > I'll have to look through the code to see if I'm depending on this > anywhere, but I don't think so. I agree that the new behavior is more > consistent. I can see some unhappiness from users expecting to use > this to avoid input handling though. Yeah - I (and I know Eric) are worried about the potential impact, but, as you say, it brings things to a more consistent point. To me that seems worthwhile. -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
