Re: [Puppet-dev] RFC - A specification for module schemas

2016-02-01 Thread Trevor Vaughan
Hi Corey, I needed to validate my data against a known set of Hiera and/or ENC data for compliance validation and did it with a function: https://github.com/trevor-vaughan/pupmod-compliance. I would *love* to see something like this hit the core language, but there are quite a few cases where I

Re: [Puppet-dev] RFC - A specification for module schemas

2016-02-01 Thread Eli Young
On Mon, Feb 1, 2016 at 11:48 AM, Trevor Vaughan wrote: > I would *love* to see something like this hit the core language, but there > are quite a few cases where I have items that can be a Boolean, Number, or > String (I'm still not loving needing to convert Numbers to

Re: [Puppet-dev] RFC - A specification for module schemas

2016-02-01 Thread Rob Nelson
Those three types will be the majority of what you use, sure, but Optional and Enum are awesome. Pattern seems potent but may be difficult to use. Check out how this module uses the type system: https://github.com/jlambert121/jlambert121-puppet/blob/master/manifests/init.pp On Monday, February 1,

Re: [Puppet-dev] RFC - A specification for module schemas

2016-02-01 Thread Trevor Vaughan
I'll give it a shot again (unfortunately, I have legacy 3.X users so updating to use 4.X features will take some time). Honestly, I still haven't found a compelling reason for anything besides Booleans, Undef, and Strings. Even the stdlib code converts everything to a string due to the issues

Re: [Puppet-dev] RFC - A specification for module schemas

2016-02-01 Thread John Bollinger
On Sunday, January 31, 2016 at 2:37:53 PM UTC-6, Corey Osman wrote: > I think we have strayed off topic here. Being able to validate hiera > should be something that can easily be done by anyone no matter which > version of puppet they use. > I agree that being able to validate Hiera data

[Puppet-dev] travis issue affecting many repos using ruby 1.9.3

2016-02-01 Thread Corey Osman
FYI There is an issue with travis and bundler on ruby version 1.9.3. So if your build matrix uses this ruby you may be seeing this error: NoMethodError: undefined method `spec' for nil:NilClass To fix you just need to update bundler like so in your travis file. before_install: #

Re: [Puppet-dev] travis issue affecting many repos using ruby 1.9.3

2016-02-01 Thread Corey Osman
It is an older issue but from 2015 but I think travis just made it come to light. Setting sudo to false may also fix the issue which maybe why your project works. I have run into with the puppetlabs_spec_helper and one of my own repos.

[Puppet-dev] Re: RFC - A specification for module schemas

2016-02-01 Thread Henrik Lindberg
There were many great replies to this, I am following up on this and the comments made elsewhere in one go here. On 2016-30-01 5:45, Corey Osman wrote: I wanted to bring up a conversation in hopes that we as a community can create a specification for something I am calling module schemas.

[Puppet-dev] Re: Puppet 4: defined resource types and epp template

2016-02-01 Thread Henrik Lindberg
On 2016-01-02 24:23, Martin Alfke wrote: Hi, I recently had an issue with epp template within a defined resource type. Let’s assume the following code snippets: # modules/test/manifests/init.pp class test { ::test::files { 'test': param1 => 'value', } } #

Re: [Puppet-dev] travis issue affecting many repos using ruby 1.9.3

2016-02-01 Thread Rob Nelson
Do you know what's triggering it? That doesn't seem like a new issue, and I see some 1.9.3 builds working without that, such as https://travis-ci.org/voxpupuli/puppet-confluence/builds/106194437 Rob Nelson rnels...@gmail.com On Mon, Feb 1, 2016 at 12:38 PM, Corey Osman