On 2014-11-04 22:46, Josh Cooper wrote:
Stefan Goethals added the ability to specify puppet's log_level in
puppet.conf[1] and it will be available in Puppet 4.0. This was
originally redmine ticket #4761, so thank you Stefan for resolving that!
I did run into one surprise and wanted to get feedba
On 11/04/2014 01:04 PM, Andy Parker wrote:
>
>
> It would also provide at lot more confidence that a manifest is 4x
> safe
> if it passes `puppet parser validate`. Without that you'd have to
> worry
> about conditional expressions silently changing their result
> between 3x
Puppet 3.7.3 is a bug fix release in the Puppet 3.7 series. It gives Windows
users the useful new `$system32` fact (due to packages now pulling in Facter
2.3), and fixes some bugs with directory environments, the `PATH` variable on
Windows, and the future parser. It also lays groundwork for some
Stefan Goethals added the ability to specify puppet's log_level in
puppet.conf[1] and it will be available in Puppet 4.0. This was originally
redmine ticket #4761, so thank you Stefan for resolving that!
I did run into one surprise and wanted to get feedback. If you specify
log_level=debug in p
On 2014-01-11 2:22, Henrik Lindberg wrote:
Yet again someone was bit by the automatic String to Numeric conversion
that is in Puppet (and also in --parser future).
The particular thing this time was
https://tickets.puppetlabs.com/browse/PUP-3602 that caused certain md5
fingerprints to look like
On 2014-04-11 18:28, Joshua Hoblitt wrote:
On 11/04/2014 09:46 AM, Henrik Lindberg wrote:
It is a bit difficult since operators are overloaded on type. The good
part is that if we stop transforming strings to numbers there will be
errors for arithmetic expressions.
The bad part is that ==, != c
On Tue, Nov 4, 2014 at 9:28 AM, Joshua Hoblitt wrote:
> On 11/04/2014 09:46 AM, Henrik Lindberg wrote:
> > It is a bit difficult since operators are overloaded on type. The good
> > part is that if we stop transforming strings to numbers there will be
> > errors for arithmetic expressions.
> >
>
On 4 November 2014 14:32, tracyde wrote:
> I am new to ruby development and want to integrate my report parser with
> TravisCI. I have read articles and blog posts on how to integrate Puppet
> modules with rspec, puppet-lint, and travisci but those are not directly
> applicable to modules that do
>
> Without that you'd have to worry about conditional expressions silently
> changing their result between 3x and 4x.
>
This x 1000. This is an absolute MUST for the release of 4.0 lest we
silently alter every system out there (terrifying).
Trevor
On Tue, Nov 4, 2014 at 5:28 PM, Joshua Hoblitt
On 11/04/2014 09:46 AM, Henrik Lindberg wrote:
> It is a bit difficult since operators are overloaded on type. The good
> part is that if we stop transforming strings to numbers there will be
> errors for arithmetic expressions.
>
> The bad part is that ==, != cannot raise errors (since a string i
On 2014-03-11 18:19, John Bollinger wrote:
On Friday, October 31, 2014 8:22:36 PM UTC-5, henrik lindberg wrote:
[...]
Yet again someone was bit by the automatic String to Numeric conversion
that is in Puppet (and also in --parser future).
I must confess to a certain dark amusement
I am new to ruby development and want to integrate my report parser with
TravisCI. I have read articles and blog posts on how to integrate Puppet
modules with rspec, puppet-lint, and travisci but those are not directly
applicable to modules that do nothing but provide lib instances (facts,
repo
12 matches
Mail list logo
