Issue #11333 has been updated by Ilya Sher.
Assignee deleted (Ilya Sher)
The only usage I see for `ensurable?` is as follows (in
`lib/puppet/metatype/manager.rb`)
` # If they've got all the necessary methods defined and they haven't
# already added the property, then do so now.
klass.ensurable if klass.ensurable? and ! klass.validproperty?(:ensure)
`
Meaning that sometimes the classes that are false-positvely classified as
ensurable
will get the `ensure` property when they shouldn't. Which should not break much
and
should not be easily observable.
----------------------------------------
Bug #11333: Incorrect Puppet::Type.ensurable? behaviour
https://projects.puppetlabs.com/issues/11333
Author: Ilya Sher
Status: Needs More Information
Priority: Normal
Assignee:
Category: plumbing
Target version:
Affected Puppet version:
Keywords:
Branch:
`Puppet::Type.ensurable?` incorrectly returns true even when
`public_method_defined?(:exists?)` is false because the check
never actually happens due to a bug. This fix handles this
and simplifies the code.
Attaching patch against commit 464a279c7425643188024ba7f98392b9057d6e35
Only tested in an isolated file, so it needs testing
(which I currently don't have the time to do.)
--
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://projects.puppetlabs.com/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.
