I agree with Adrien. I think the solution will be something with a benefit for
the entire RAL.
The thought I have is of a solution that preserves the original behavior of
having a resource type auto-discover it’s preferred provider on a system. So in
this case, we could allow one resource per
> > There is a hook for types that gets called when catalog compilation is
> > complete, but it then only calls the relationship params giving them a
> > chance to resolve their relationships. I'm currently working on a pull
> > request to change that situation though.
> >
>
> Could you give s
This issue is also hindering me as well. I have some disparate types that
update sections of a mapped XML document they all share. Anyway, here is my
attempt, in the form of a pull request!
https://github.com/puppetlabs/puppet/pull/1800
In the mean time, I'm going to try to test some of the alt
