On 30/03/16 23:12, Jeremiah Powell wrote:
ASTs don't need to be built on a node-by-node basis (unless you
meant manifest-by-manifest basis
Well, manifest-by-manifest where the manifest will vary depending on the
node the compile job is depending upon. Reviewing the code I get the
impre
>
> ASTs don't need to be built on a node-by-node basis (unless you meant
> manifest-by-manifest basis
>
Well, manifest-by-manifest where the manifest will vary depending on the
node the compile job is depending upon. Reviewing the code I get the
impression I just don't understand the existing pa
Hi Jeremiah,
On Wed, Mar 30, 2016 at 11:56 AM, wrote:
> I write a lot of native types for our internal use at work. (I tell
> people that if you are just using Exec in Puppet that ansible is one search
> away in Google. ) Some of the Puppet code used with these types would be
> very challenging
I write a lot of native types for our internal use at work. (I tell people
that if you are just using Exec in Puppet that ansible is one search away
in Google. ) Some of the Puppet code used with these types would be very
challenging to "pre-compile" in any way.
I think a lot of my questions a
Hi, I've just posted a new Puppet RFC that describes pre-parsed and
pre-validated Puppet files, akin to '.pyc' files for Python. It's called
XPP and the doc is open for comments here:
https://docs.google.com/document/d/17SFn_2PJYcO5HjgA4R65a5ynR6_bng_Ak5W53KjM4F8/edit?usp=sharing
Please comment
This confirms the removal of stable and testing from apt.puppetlabs.com. All
packages are available under their codenames (jessie, wheezy, etc).
--
Rick Sherman
Release Engineering, Puppet Labs
On Wednesday, February 24, 2016 at 5:42:09 PM UTC-6, Melissa Stone wrote:
> We've stopped using the
