Jira (PUP-867) Deprecate Dynamically Scope Resource Defaults

Ethan Brown (JIRA) Tue, 27 May 2014 10:48:07 -0700

Title: Message Title

Ethan Brown commented on an issue

With current parser, the behavior is the same before / after the PR. I had checked this out locally, but only for my own sake as I wasn't sure from the comment thread what the expectation is.

                                                    [puppet] bundle exec puppet apply notice.pp --parser=current                                                 10:32:29  ☁  master ☂ ✭
Notice: Compiled catalog for ethans-mbp.corp.puppetlabs.net in environment production in 0.02 seconds
Notice: defaulted
Notice: /Stage[main]/B/Notify[hi]/message: defined 'message' as 'defaulted'
Notice: defaulted
Notice: /Stage[main]/A/Notify[bye]/message: defined 'message' as 'defaulted'
Notice: Finished catalog run in 0.02 seconds

                                                

Given this meets your expectations, I'm resolving.

Thanks for the info.

Add Comment

Puppet /

PUP-867

Currently the manifest
{code}
class a {
  Notify {
    message => "defaulted"
  }
  include b

  notify { bye: }
}

class b {
  notify { hi: }
}

include a
{code}

results in
{code}
Notice: Compiled catalog for aparker.delivery.puppetlabs.net in environment production in 0.02 seconds
Notice: defaulted
Notice: /Stage[main]/B/Notify[h...

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-867) Deprecate Dynamically Scope Resource Defaults

Reply via email to