On 2015-15-05 24:59, Joshua hoblitt wrote:
As I'm slowly updating my modules' testing boilerplate for puppet 4.x,
I've run into a couple cases of breakage that I'm unsure if they are
intentional changes in semantics or regressions.
When introspecting on a resource and the param is undefined, an
On May 14, 2015, at 12:11 PM, Spencer Krum n...@spencerkrum.com wrote:
Hi Folks,
There is currently a PR against stdlib that I am writing to you today
about: https://github.com/puppetlabs/puppetlabs-stdlib/pull/444
Thanks to Spredzy for making this PR.
This is tracked in jira:
In the next few weeks we’ll be releasing facter 3, a native (compiled
C++11) implementation of facter. Note that the only packages containing
facter 3 will be the puppet-agent packages (e.g. there will be no facter 3
gems).
This change may have some workflow implications for module developers,
On May 14, 2015, at 4:00 PM, Erik Dalén erik.gustav.da...@gmail.com wrote:
On Thu, 14 May 2015 at 21:45 Trevor Vaughan tvaug...@onyxpoint.com
mailto:tvaug...@onyxpoint.com wrote:
Hmmwhat about a concept of deferred actions?
I.e. Try this resource, can't do it, shove it (and it's
On Thursday, May 14, 2015 at 5:59:49 PM UTC-5, Joshua Hoblitt wrote:
It appears that classes are no longer a first class resource.
Classes have *never* been a first class resource, though for a time there
was a concerted effort to give that impression.
John
--
You received this message
On Thursday, May 14, 2015 at 2:45:52 PM UTC-5, Trevor Vaughan wrote:
Hmmwhat about a concept of deferred actions?
I.e. Try this resource, can't do it, shove it (and it's dependencies) to
the bottom of the stack and do everything else, then come back to it.
Yes. If there's a
I was actually really hoping for multi-threaded catalog application but I
realized that 99% of the time I don't want it because I'm already pegging
one processor working on the system.
Also, the code complexity that comes with that probably isn't worthwhile.
HOWEVER, if we take the idea above
