On Mon, Oct 6, 2014 at 2:01 PM, Jeff McCune wrote:
> I think we should do 2a because there should be rough parity between the
> configuration files and the command line arguments. We should do 2 or 2a
> because as John says, Puppet should, "Stop getting in my way!"
I think that option 2a is th
Sorry to resurrect an old thread, but this came to my attention again today.
On Fri, Mar 14, 2014 at 6:20 AM, John Bollinger
wrote:
>
>
> On Thursday, March 13, 2014 8:50:19 AM UTC-5, Trevor Vaughan wrote:
>>
>> SecondaryPackage wouldn't fix it if you wanted to install using pip and
>> gem on th
On Mon, Oct 6, 2014 at 1:26 PM, John Bollinger
wrote:
>
> I'm going to think a little more and see what others have to say before I
> come down on the question of (2) vs. (2a).
>
I think we should do 2a because there should be rough parity between the
configuration files and the command line argu
On Sunday, October 5, 2014 8:30:32 PM UTC-5, Felix Frank wrote:
>
>
> We're now looking for feedback on whether apply should get the same
> semantics, for masterless operation.
>
> There are three alternatives here that I can see:
>
> 1. Status quo - ruthlessly override whatever the ENC specif
Puppet Server 0.2.2 is a bugfix release.
The following bugs and issues are addressed in this release:
* SERVER-13 [1]: Fix for file descriptor leak when using an https report
processor such as PuppetDB or Foreman
* HTTPS client connections created by Puppet Server now use the CA cert
specified by
Thank you very much!
воскресенье, 5 октября 2014 г., 23:30:33 UTC+4 пользователь Felix Frank
написал:
>
> Hi,
>
> this type of question would be better suited for the puppet-users list.
>
> The problem is that variable values *cannot* be overridden. You just
> replace its value in the scope of
