Issue #18787 has been updated by Rob Nelson. Status changed from Unreviewed to Accepted
Seems like a reasonable request, triaged as part of the Oct 2013 Triage-a-Thon. ---------------------------------------- Feature #18787: Include information about why a provider is unsuitable https://projects.puppetlabs.com/issues/18787#change-98271 * Author: Nick Lewis * Status: Accepted * Priority: Normal * Assignee: * Category: * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- If a provider has a confine on some feature, or fact, or requires some command and that feature/command/fact is missing/wrong, the provider will be considered unsuitable. We display an error message when you try to use it, but the only information that error message has is that the provider is unsuitable. Given that all of those sorts of confines are declarative, we ought to be able to explain *why* the provider was unsuitable. For instance, "Provider rpm is not functional on this host, because the 'rpm' command is not available". Probably, failed confines should take precedence over missing commands, because commands usually won't exist if a confine fails (if you're not on darwin, you're not going to have any of the three launchd-related commands, but it's redundant to mention that). -- 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 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/groups/opt_out.
