On Fri, Jan 10, 2014 at 12:55 PM, Dustin J. Mitchell <dus...@v.igoro.us>wrote:

> On Fri, Jan 10, 2014 at 12:45 PM, Andy Parker <a...@puppetlabs.com> wrote:
> > Tier-1 types: user, service, file, group, package, host, cron, exec,
> stage,
> > tidy
> > Tier-1 providers: dpkg, apt, gem, msi, rpm, windows, yum, useradd,
> > windows_adsi, groupadd, crontab
> >
> > everything else is tier-2.
>
> I'd like to see augeas be Tier-1.  I think of that as a more powerful
> version of file, really.  But if that's not how it's maintained, c'est
> la vie.  In other words, if I'm asking for PL to take on more
> maintenance burden than currently, then my request is out of scope for
> this conversation.
>
> Also, it seems like 'notify' is simple enough to include, and
> 'resources' and 'schedule' are pretty core to the language.
>
> Other than that, I agree.
>

I'm not sure I'd stick 'mount' in tier2, but that's the only other thing I
can think of.  I'm late to the party but I want to throw my support behind
Daniel's plan to move all tier2 stuff into modules, right from the start,
and ship known tested versions with Puppet.

As part of the module team I think we'd have an easier time pitching in to
help with the maintenance of these (such as helping with PRs and testing)
if they were in modules like the rest of our stuff.  We're building out
internal infrastructure to acceptance test our "supported modules" on our
PE platforms and it wouldn't be much of a stretch to eventually bring these
into that concept and have us specifically work on improving the test
situation around these.

Thanks,

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/CAPfZVDZhw_7bL5z0JOwS6mVp-5rNONbUEXjrgyVTNLyYpXL1%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to