Hi Rob,
Thanks for posting that, this is probably the best practical example that
I've seen so far.
Trevor
On Mon, Feb 1, 2016 at 9:27 PM, Rob Nelson wrote:
> Those three types will be the majority of what you use, sure, but Optional
> and Enum are awesome. Pattern seems
" <co...@logicminds.biz>
>> > To: "puppet-dev" <puppe...@googlegroups.com>
>> > Sent: Saturday, January 30, 2016 7:47:03 PM
>> > Subject: Re: [Puppet-dev] RFC - A specification for module schemas
>>
>> > On Friday, January 29, 2016 at 1
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
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,
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
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
> From: "Corey Osman" <co...@logicminds.biz >
> >> > To: "puppet-dev" <puppe...@googlegroups.com >
> >> > Sent: Saturday, January 30, 2016 5:45:05 AM
> >> > Subject: [Puppet-dev] RFC - A specification for module schemas
> >&g
On Friday, January 29, 2016 at 10:47:48 PM UTC-8, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "Corey Osman" <co...@logicminds.biz >
> > To: "puppet-dev" <puppe...@googlegroups.com >
> > Sent: Saturd
I think there are some interesting ideas here but I want to pull out
the problems, and then jot down a few thoughts. Lots of comments
inline.
On 30 January 2016 at 04:45, Corey Osman wrote:
> Hi,
>
> I wanted to bring up a conversation in hopes that we as a community can
>
On Saturday, January 30, 2016 at 9:29:02 AM UTC-8, Gareth Rushgrove wrote:
>
> I think there are some interesting ideas here but I want to pull out
> the problems, and then jot down a few thoughts. Lots of comments
> inline.
>
>
> On 30 January 2016 at 04:45, Corey Osman
- Original Message -
> From: "Corey Osman" <co...@logicminds.biz>
> To: "puppet-dev" <puppet-dev@googlegroups.com>
> Sent: Saturday, January 30, 2016 7:47:03 PM
> Subject: Re: [Puppet-dev] RFC - A specification for module schemas
> On Fri
- Original Message -
> From: "Corey Osman" <co...@logicminds.biz>
> To: "puppet-dev" <puppet-dev@googlegroups.com>
> Sent: Saturday, January 30, 2016 5:45:05 AM
> Subject: [Puppet-dev] RFC - A specification for module schemas
> Hi,
&g
Hi,
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. Before I get into
that I want to provide a little background info.
This all started a few years ago when hiera first came out. Data seperation in
the
13 matches
Mail list logo