The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
documentation gap for non-trivial providers and types
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
(this bug being filed as per discussion on dev mailing list)
There is a lacking in the documentation for non-trivial resource providers. http://docs.puppetlabs.com/guides/complete_resource_example.html gives a fairly trivial “example”. There are no additional stepping stones given to implement a more interesting, yet “clean” provider. (one that is more fully featured, yet needs no back-end additional hacks such as the “user” class)
Additional information such as “ensurable” can be expanded to a full clause with subpproperties.
(Longer discussion at https://groups.google.com/forum/?fromgroups#!topic/puppet-dev/jX8NQvdYQEA)
#5 Updated by Nick Fagerlund about 2 years ago
- Status changed from Rejected to Closed
I’m closing this ticket for housekeeping reasons, since we’re moving to a new ticketing system at https://tickets.puppetlabs.com.
There’s not a direct analogue to this ticket in the new tracker yet. If you’re still interested in this issue, you can make a new ticket once the new tracker goes publicly available in several days.
For this particular ticket, overhauling the type/provider docs is a big enough deal that we’ll be treating it as planned work and making probably a dozen sub-tickets once we’ve dealt with our current priorities. In the meantime, though, we won’t be tracking that work in Redmine. Sorry for any confusion I caused by marking this as “rejected!”