Re: the yard docs, I think they are generally pretty good for API docs, and
it looks like most of the stuff is in fact documented in the code, but not
appearing in generated output for some reason. I took a quick look but
didn't see any obvious reason for this. I'd be willing to donate some spar
Hi Henrik or Eric,
Is it possible to error on failed lookups? This is useful for replacing the
fail('osfamily not supported') lines in most params.pp files. Ryan
mentioned the same thing in the ticket and I wasn't sure if it was resolved.
It currently returns undef if the value is not found.
This isn't just an optimization. There are cases where you must
resort to exec'ing yum when, for example, two interdependent packages
must be installed in the same transaction, or one incompatible package
must be replaced by another. Note that the latter entails installing
and removing in the sam
I tried asking this in users and I'm not sure if that was the best place,
so I'll try here. It's probably best to start off by explaining *why* I
would ever want to do this. There are edge cases that have been around
since the long long ago that are hard to meet with puppet. These mainly
sur
In the announcement, http://projects.puppetlabs.com/issues/16856 is
introduced as data in modules, and that we should see ARM-9 (
https://github.com/puppetlabs/armatures/blob/master/arm-9.data_in_modules/index.md
).
But #16856 itself never references ARM-9 that I can see, but only
references
