On 09/23/2015 02:17 AM, Cody Herriges wrote:
> Alex Schultz wrote:
>> Hey puppet folks,
>>
>> Based on the meeting yesterday[0], I had proposed creating a parser
>> function called is_service_default[1] to validate if a variable matched
>> our agreed upon value of ''. This got me thinking
>>
+1 to way from paste above.
2015-09-23 16:42 GMT+03:00 Martin Mágr :
>
>
> On 09/23/2015 02:17 AM, Cody Herriges wrote:
>
> Alex Schultz wrote:
>
> Hey puppet folks,
>
> Based on the meeting yesterday[0], I had proposed creating a parser
> function called is_service_default[1]
>
> I've been mulling this over the last several days and I just can't
> accept an entire ruby function which would be ran for every parameter
> with the desired static value of "" when the class is
> declared and parsed. I am not generally against using functions as a
> parameter default just
On 09/23/2015 02:17 AM, Cody Herriges wrote:
Alex Schultz wrote:
Hey puppet folks,
Based on the meeting yesterday[0], I had proposed creating a parser
function called is_service_default[1] to validate if a variable matched
our agreed upon value of ''. This got me thinking
about how can we
Alex Schultz wrote:
>> I've been mulling this over the last several days and I just can't
>> accept an entire ruby function which would be ran for every parameter
>> with the desired static value of "" when the class is
>> declared and parsed. I am not generally against using functions as a
>>
On Wed, Sep 23, 2015 at 11:46 AM, Cody Herriges wrote:
> Alex Schultz wrote:
>>> I've been mulling this over the last several days and I just can't
>>> accept an entire ruby function which would be ran for every parameter
>>> with the desired static value of "" when the class
On 09/22/2015 08:17 PM, Cody Herriges wrote:
> Alex Schultz wrote:
>> Hey puppet folks,
>>
>> Based on the meeting yesterday[0], I had proposed creating a parser
>> function called is_service_default[1] to validate if a variable matched
>> our agreed upon value of ''. This got me thinking
>>
Alex Schultz wrote:
> Hey puppet folks,
>
> Based on the meeting yesterday[0], I had proposed creating a parser
> function called is_service_default[1] to validate if a variable matched
> our agreed upon value of ''. This got me thinking
> about how can we maybe not use the arbitrary string
On 09/16/2015 09:39 PM, Emilien Macchi wrote:
>
> On 09/16/2015 12:53 PM, Alex Schultz wrote:
>> Hey puppet folks,
>>
>> Based on the meeting yesterday[0], I had proposed creating a parser
>> function called is_service_default[1] to validate if a variable matched
>> our agreed upon value of ''.
Clint,
We're solving a different issue. Before anytime someone added an option we
had this logic:
if $setting {
project_config/setting: value => $setting
}
else {
project_config/setting: ensure => absent;
}
This was annoying to have to write for every single setting but without it,
nobody
Excerpts from Alex Schultz's message of 2015-09-16 09:53:10 -0700:
> Hey puppet folks,
>
> Based on the meeting yesterday[0], I had proposed creating a parser
> function called is_service_default[1] to validate if a variable matched our
> agreed upon value of ''. This got me thinking about how
>
Hey puppet folks,
Based on the meeting yesterday[0], I had proposed creating a parser
function called is_service_default[1] to validate if a variable matched our
agreed upon value of ''. This got me thinking about how
can we maybe not use the arbitrary string throughout the puppet that can
not
On 09/16/2015 12:53 PM, Alex Schultz wrote:
> Hey puppet folks,
>
> Based on the meeting yesterday[0], I had proposed creating a parser
> function called is_service_default[1] to validate if a variable matched
> our agreed upon value of ''. This got me thinking
> about how can we maybe not use
Emilien Macchi wrote:
>
> On 09/16/2015 12:53 PM, Alex Schultz wrote:
>> Hey puppet folks,
>>
>> Based on the meeting yesterday[0], I had proposed creating a parser
>> function called is_service_default[1] to validate if a variable matched
>> our agreed upon value of ''. This got me thinking
>>
14 matches
Mail list logo