On Thursday, November 6, 2014 12:39:22 PM UTC+1, Felix Frank wrote:
>
> On 11/06/2014 12:04 PM, Luke Kanies wrote:
> > A fourth option would be to combine the best of Resources and exported
> > resources: Build a querying system akin to exported resources, but
> > against the current system, rather than against the catalog. Or really,
> > take the exact same querying we already have, but provide the ability to
> > control where it's searching against, and what to do with the results.
> >
> > This is my preferred solution. It makes querying more powerful, and
> > separates the concept of querying from the source of the data.
>
> This is a very attractive idea.
>
> Currently the purging through resources is likely to appear entirely too
> mystical to most users.
>
> To get a behavior that matches today's resources type, we'd need to
> explicitly query unmanaged resources.
>
> User<~| managed == false |~> { ensure => absent }
>
>
One thing I really like about this option is the possibility to set these
resources to something else than "absent". For example, you might want to
ensure that unmanaged packages are purged or that unmanaged services are
stopped.
--
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/a3b35edb-d693-45a8-bd2a-bb7144af82bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
