Hunter Haugen writes:
> We actually have a load of tickets in our next sprint to enable future
> parser testing on all of the supported modules and go through making them
> compatible, starting Oct 1st. Good timing on your question, bad timing that
> it's taken us this long to get to it :(.
On 2014-30-09 24:30, Hunter Haugen wrote:
On Thu, Sep 18, 2014 at 2:16 PM, Tim Skirvin mailto:tskir...@fnal.gov>> wrote:
I decided to try out 'parser = future' today, and the first
thing
to fail was puppetlabs-apache, with errors along the lines of:
Filepath:
On Thu, Sep 18, 2014 at 2:16 PM, Tim Skirvin wrote:
> I decided to try out 'parser = future' today, and the first thing
> to fail was puppetlabs-apache, with errors along the lines of:
>
> Filepath:
> /srv/puppet/env/puppet/modules/apache/templates/httpd.conf.erb
> Line: 19
>
Yeah. I found an error in the puppetlabs-mcollective module (
https://tickets.puppetlabs.com/browse/MODULES-1192) where it doesn't work
with "trusted_node_data = true", which per the docs is a 3.6.2 recommended
safe setting. When I was testing my fix, I made the mistake of running
specs with future
+1 for a plan for this
On Thu, Sep 18, 2014 at 2:16 PM, Tim Skirvin wrote:
> I decided to try out 'parser = future' today, and the first thing
> to fail was puppetlabs-apache, with errors along the lines of:
>
> Filepath:
> /srv/puppet/env/puppet/modules/apache/templates/httpd.conf.e
I decided to try out 'parser = future' today, and the first thing
to fail was puppetlabs-apache, with errors along the lines of:
Filepath: /srv/puppet/env/puppet/modules/apache/templates/httpd.conf.erb
Line: 19
Detail: comparison of Float with String failed
There's alr
