Re: [Puppet-dev] Re: Decision: Near future of resource expressions

Sorry for the vagueness. I was referring to Geppetto, the Vim plugin, etc... Random parenthesis are something that I think will be often overlooked without some help. Thanks, Trevor On Mon, Aug 4, 2014 at 7:16 PM, Henrik Lindberg < henrik.lindb...@cloudsmith.com> wrote: > On 2014-05-08 1:08,

[Puppet-dev] Re: Decision: Near future of resource expressions

On 2014-05-08 1:08, Trevor Vaughan wrote: This is certainly better than the new operator but the parenthesis are a bit strange. Isn't the title 'default' special enough to not have the parenthesis? The functionality is not limited to the default title, and a literal default is not a special ex

Re: [Puppet-dev] Re: Decision: Near future of resource expressions

This is certainly better than the new operator but the parenthesis are a bit strange. Isn't the title 'default' special enough to not have the parenthesis? If not, then I can certainly live with the parenthesis syntax better than a new operator (though support in the syntax checkers will be most

[Puppet-dev] Re: Decision: Near future of resource expressions

On 2014-04-08 20:35, Trevor Vaughan wrote: So, I'm chiming in to say that I completely agree with Reid and Ashley. As an end user, I want to hand off code that is clear and relatively easy to read. I definitely do not want magic symbols (or I would have stuck with PERL). I'm OK with all of the

Re: [Puppet-dev] Re: Decision: Near future of resource expressions

So, I'm chiming in to say that I completely agree with Reid and Ashley. As an end user, I want to hand off code that is clear and relatively easy to read. I definitely do not want magic symbols (or I would have stuck with PERL). I'm OK with all of the concepts proposed but I would like more verbo

Re: [Puppet-dev] Re: Decision: Near future of resource expressions

On Mon, Aug 4, 2014 at 12:09 PM, Reid Vandewiele wrote: > > > I am concerned that adding additional operators to the language does in > fact take something away. As such, I do think that proposals to do so need > to require a very strong argument in order to proceed. > > When I go out and introduc

[Puppet-dev] Re: Decision: Near future of resource expressions

On Sunday, August 3, 2014 4:32:39 PM UTC-7, henrik lindberg wrote: > > > My main objection with create_resources function is that it is not a > natural progression from the language. When developing puppet code, you > start out with simple resources and use the syntax for creating them. As > y

Re: [Puppet-dev] Decision: Near future of resource expressions

On Sun, Aug 3, 2014 at 1:22 PM, Luke Kanies wrote: > On Jul 28, 2014, at 7:33 AM, Henrik Lindberg < > henrik.lindb...@cloudsmith.com> wrote: > > > On 2014-28-07 8:34, Luke Kanies wrote: > >> On Jul 24, 2014, at 5:32 PM, Andy Parker >> > wrote: > >> > >>> Howdy, > >>>

Re: [Puppet-dev] Presenting a custom error message if source file in module does not exist

On 2014-08-02 07:55, Craig Barr wrote: TL;DR How do I output a custom error message for a failed assertion that a source file exists. In other words, how do I display a nice error message when puppet:///modules/mymodule/mysourcefile.txt does not exist A great way to improve the situation would

Re: [Puppet-dev] if statement not being parsed when trying to select omit the ensure parameter from a resource.

On 2014-08-02 06:19, Thom Luxford wrote: The intention is for the the service running state after boot to be optionally handled by puppet. Omitting the ensure parameter does this, but why can't I add it when I need it like this? service { "$my_module::params::myServiceName": if $::my_servic

Re: [Puppet-dev] Presenting a custom error message if source file in module does not exist

On 08/02/2014 07:55 AM, Craig Barr wrote: > TL;DR How do I output a custom error message for a failed assertion that > a source file exists. In other words, how do I display a nice error > message when puppet:///modules/mymodule/mysourcefile.txt does not exist Hi, this feels like more of a puppet

[Puppet-dev] Presenting a custom error message if source file in module does not exist

This feels like a beginner question so apologies to the experts out there reading this. Please skip to the last line of this post for the 'shortened version of this question'. For my module, I believe there is a high likelihood the user may not copy a required source file to the module 'files'

[Puppet-dev] if statement not being parsed when trying to select omit the ensure parameter from a resource.

The intention is for the the service running state after boot to be optionally handled by puppet. Omitting the ensure parameter does this, but why can't I add it when I need it like this? service { "$my_module::params::myServiceName": if $::my_service_ensure_running != 'undef' { ensu