Re: [Puppet-dev] Leaving Puppet Labs

was doing with the language/server team. That will continue until Henrik decides that it is his fate or someone else steps up or is found :) > On Wed Nov 05 2014 at 6:28:23 PM Andy Parker wrote: > >> This is one of the hardest emails that I've ever had to write, but the >> best

[Puppet-dev] puppet-dev status week ending 2014-11-06

** Next PR Triage Wednesday, November 12th @ 10:00 am Pacific. ** Priorities 1. Puppet 3.7.4 2. Native Facter 0.3.0 3. Puppet-server 0.4.0 4. Code removal for puppet 4 5. New puppet doc implementation Commentary This email is being put together a little diffe

Re: [Puppet-dev] How should apply behave under an ENC

On Wed, Oct 22, 2014 at 1:46 PM, John Bollinger wrote: > On Tuesday, October 21, 2014 3:40:19 PM UTC-5, Felix Frank wrote: >> >> All things considered, we find ourselves in a fine position to choose >> our poison. There were more votes from the 2/2a camps, but also good >> points from RI in favor

[Puppet-dev] Leaving Puppet Labs

This is one of the hardest emails that I've ever had to write, but the best way, I suppose, is to get the really hard part out of the way first. I've decided to move on from my time at Puppet Labs. My last day will be November 14th. My reason for leaving is pretty non-spectacular: after working re

Re: [Puppet-dev] Re: The string to number torture never stops

On Tue, Nov 4, 2014 at 9:28 AM, Joshua Hoblitt wrote: > On 11/04/2014 09:46 AM, Henrik Lindberg wrote: > > It is a bit difficult since operators are overloaded on type. The good > > part is that if we stop transforming strings to numbers there will be > > errors for arithmetic expressions. > > >

[Puppet-dev] Platform Team Week of October 27th, 2014

** Next PR Triage Wednesday, November 5th @ 10:00 am Pacific. ** *Priorities* 1. Puppet 3.7.3 2. CFacter on the march 3. New puppet doc implementation 4. Code removal for puppet 4 *Commentary* We are still working on a Puppet 3.7.3. Why are we having so many releases of 3.7? Well,

Re: [Puppet-dev] Switching from YAML and PSON to JSON

On Fri, Oct 24, 2014 at 1:58 PM, Joshua Hoblitt wrote: > On 10/24/2014 11:49 AM, Wil Cooley wrote: > > On the other hand, I'm more likely to try to run grep on the master, > which > > does not work well with minimized JSON (I'm clever enough that I can do > it, > > but I would curse under my brea

Re: [Puppet-dev] Re: Switching from YAML and PSON to JSON

On Fri, Oct 24, 2014 at 10:48 AM, Luke Kanies wrote: > On Oct 24, 2014, at 9:59 AM, Andy Parker wrote: > > On Fri, Oct 24, 2014 at 2:47 AM, Erik Dalén > wrote: > >> On 24 October 2014 03:24, Henrik Lindberg > > wrote: >> >>> On 2014-24-10 2:04,

Re: [Puppet-dev] Switching from YAML and PSON to JSON

On Fri, Oct 24, 2014 at 9:30 AM, Wil Cooley wrote: > > On Oct 23, 2014 5:04 PM, "Andy Parker" wrote: > > > > So what all would be changing? > ... > > 2. YAML files that the master and agent write would move to JSON > (node, facts, last_run_summary, sta

Re: [Puppet-dev] Re: Switching from YAML and PSON to JSON

On Fri, Oct 24, 2014 at 2:47 AM, Erik Dalén wrote: > On 24 October 2014 03:24, Henrik Lindberg > wrote: > >> On 2014-24-10 2:04, Andy Parker wrote: >> >>> A while ago we removed support for puppet to *send* YAML on the network. >>> At the same time we con

Re: [Puppet-dev] Platform Team Week of October 20th, 2014

On Thu, Oct 23, 2014 at 4:03 PM, Erik Dalén wrote: > > > On 23 October 2014 20:53, Andy Parker wrote: > >> ** Next PR Triage Wednesday, October 29th @ 10:00 am Pacific. ** >> >> *Priorities* >> >>1. Puppet 3.7.3 >>2. CFacter on the marc

[Puppet-dev] Switching from YAML and PSON to JSON

A while ago we removed support for puppet to *send* YAML on the network. At the same time we converted to using safe_yaml for receiving YAML in order to keep compatibility with existing agents. Instead of YAML all of the communication was done with PSON, which is a variant of JSON that has been in

[Puppet-dev] Platform Team Week of October 20th, 2014

** Next PR Triage Wednesday, October 29th @ 10:00 am Pacific. ** *Priorities* 1. Puppet 3.7.3 2. CFacter on the march 3. New puppet doc implementation 4. Code removal for puppet 4 *Commentary* Puppet 3.7.2 is released! There are a couple tickets that didn't make the boat (PUP-3302, P

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

On Tue, Oct 14, 2014 at 5:13 AM, Trevor Vaughan wrote: > I think that dropping isomorphism would be clearer to end users. > > Maybe, maybe not. I don't think that they'll often see a difference between the two. Since dropping constraints is easier than adding constraints, I think we'll go with C

Re: [Puppet-dev] Some analysis of profiling information

into memory at once. 1: https://github.com/adrienthebo/puppet-profile-parser 2: https://github.com/puppetlabs/puppet-master-profiler > - Original Message - > > From: "Andy Parker" > > To: "puppet-dev" > > Sent: Monday, October 13, 2014 6:08:22 PM > >

[Puppet-dev] Some analysis of profiling information

Last week we got our first bit of data from profiling someone's master. There were three different masters profiled and over the weekend I analyzed one of them. Here are the results of that analsys: = 8 processors ~18 hour time period (Wed Oct 0

Re: [Puppet-dev] Re: Experiences with the new type system

On Fri, Oct 10, 2014 at 10:02 AM, Daniele Sluijters < daniele.sluijt...@gmail.com> wrote: > Hi, > > Presumably you want the key => undef to represent that you want some > sort of default value that is different from key not being set at all? > There is yet another symbolic value that be used for t

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

On Thu, Oct 9, 2014 at 3:10 PM, John Bollinger wrote: > On Thursday, October 9, 2014 9:12:41 AM UTC-5, Felix Frank wrote: >> >> On 10/08/2014 10:34 PM, Charlie Sharpsteen wrote: >> > On Wednesday, October 8, 2014 11:51:32 AM UTC-7, John Bollinger wrote: >> > >> > >> > >> > On Wednesday, Octob

Re: [Puppet-dev] how can i get each java version in each custom facts

0> logfile = '/home/suppalapati/java.txt' >> => "/home/suppalapati/java.txt" >> irb(main):002:0> line_num=0 >> => 0 >> irb(main):004:0> require 'facter/util/file_read' >> => true >> irb(main):005:0> log =

Re: [Puppet-dev] how can i get each java version in each custom facts

>> If you try running one of these lines you'll see what is happening: >> >> 1.9.1 :012 > javaid, val = %x{java} >> ...lots of output... >> 1.9.1 :013 > javaid >> ...same output as above... >> 1.9.1 :014 > val >> => nil >> >&g

Re: [Puppet-dev] how can i get each java version in each custom facts

you are looking for. > *Facter.add("java_#{javaid}") do* > * setcode do* > * val* > > > Can you correct me? > > > Thank You > > On Wed, Oct 8, 2014 at 3:26 PM, Andy Parker wrote: > >> On Wed, Oct 8, 2014 at 11:26 AM, Supriya Upp

Re: [Puppet-dev] how can i get each java version in each custom facts

On Wed, Oct 8, 2014 at 11:26 AM, Supriya Uppalapati < supriya.uppalap...@gmail.com> wrote: > Hi All, > > I am trying to get all the java versions and paths where it is located. I > got all java_paths in a fact called java_path. Now i need those versions in > each custom facts. > > I wrote a code b

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

On Wed, Oct 8, 2014 at 6:33 AM, Felix Frank wrote: > On 10/08/2014 03:23 PM, Trevor Vaughan wrote: > > > > If you go with the descriptive namevar, you'll need to make the > > separator something that won't show up in a package name. So probably > > one of '+/,|' etc... > > That's not what I'm say

Re: [Puppet-dev] Package duplicate resource issue - PUP-1073

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

Re: [Puppet-dev] Announce: Puppet Server 0.2.0

On Mon, Sep 29, 2014 at 1:00 PM, Josko Plazonic wrote: > Hullo, > > On 09/23/2014 12:11 PM, Nate Wolfe wrote: > >> As the version number 0.2.0 should imply, Puppet Server is not production >> ready (yet), but please >> do try it out in your favorite sandbox. >> > > I didn't find so far any featur

Re: [Puppet-dev] Puppet Master Profiles

On Mon, Sep 29, 2014 at 10:27 AM, Dean Wilson wrote: > On 29 September 2014 18:20, Andy Parker wrote: > > We haven't gotten any responses to this yet. :( Getting this information > > will really help in allowing us to target the right places for > performance > >

Re: [Puppet-dev] Puppet Master Profiles

On Mon, Sep 22, 2014 at 10:04 AM, Britt Gresham wrote: > Hello, > > We are interested in collecting puppet profile data from the puppet master > in the real world. This data will be used to help us find a direction to go > to increase the throughput of the puppet master master. > > We haven't got

Re: [Puppet-dev] Announce: Puppet Server 0.2.0

On Fri, Sep 26, 2014 at 11:35 AM, Darin Perusich wrote: > Is there any documention on compiling puppet-server from source? I > need to be able to build it in an environment w/o network access, Open > Build Service, and I'm trying figure out all the dependencies I'm > missing. > There is a docume

Re: [Puppet-dev] pre-conf dinner and/or drinks

Let's meet at the Leland Tea Company at 3pm. Just in time for afternoon tea :) On Thu, Sep 18, 2014 at 11:40 PM, Kylo Ginsberg wrote: > That sounds great! I'm in for an afternoon meet-up (tea or GG park both > sound good). I have dinner plans, so I'll play post-dinner drinks by ear. > > On Thu,

Re: [Puppet-dev] pre-conf dinner and/or drinks

On Thu, Sep 18, 2014 at 12:10 PM, Daniele Sluijters < daniele.sluijt...@gmail.com> wrote: > Hiya everyone, > > PuppetConf is almost upon us. I'm sure most of you will be at the > Contributors summit on Monday and some of you at the speaker dinner but I > figured it would be fun to have a little pr

Re: [Puppet-dev] PR Triage canceled today

On Thu, Sep 18, 2014 at 3:18 PM, Felix Frank < felix.fr...@alumni.tu-berlin.de> wrote: > On 09/17/2014 04:57 PM, Kylo Ginsberg wrote: > > Sorry for the late notice, but Ethan and I are both working hard on > > our PuppetConf talks. As always, feel free to ping one of us on IRC re > > any PRs in fl

[Puppet-dev] Platform Team Week of September 8th, 2014

** Next PR Triage Wednesday, October 1st @ 10:00 am Pacific. ** Skipping next week because of PuppetConf Priorities 1. Puppet 3.7.1 2. CFacter on the march 3. New puppet doc implementation 4. Code removal for puppet 4 Commentary I'm still a little messed up. I don't know if this is lat

[Puppet-dev] Is this the right fix for PUP-1106?

Adrien has put together a change to address PUP-1106 (failed dependencies are not honored on refresh), however this is a really thorny issue and I'd like to get some more eyes on it before committing to the change. I think the original bug in redmine has the most history ( http://projects.puppetla

Re: [Puppet-dev] How to use 'commands' method in ruby code outside of puppet?

On Fri, Sep 12, 2014 at 11:11 AM, Jakov Sosic wrote: > Hi, > > I asked on puppet-users but I think I made a mistake, this seems to me > more like a question for puppet-dev. Sorry if it's not :( > > > So, to allow me to easier debug my providers, I sometimes wanna use > 'command' in my own ruby co

[Puppet-dev] Announce: Puppet 3.7.1 Released!

Puppet 3.7.1 is a backward-compatible bugfix release in the Puppet 3 series. This release fixes several regressions and other issues. * PUP-3222: Windows service provider references a non-existent class * PUP-3190: "each" no longer supported in Puppet 3.7.0 * PUP-3191: Syml

[Puppet-dev] Re: Platform Team Week of September 1st, 2014

On Tue, Sep 9, 2014 at 10:14 AM, Andy Parker wrote: > > ** Next PR Triage Wednesday, September 17th @ 10:00 am Pacific. ** > > Priorities > > > 1. Puppet 3.7.1 > 2. CFacter on the march > 3. New puppet doc implementation > 4. Code removal for puppet 4 > &

[Puppet-dev] Platform Team Week of September 1st, 2014

** Next PR Triage Wednesday, September 17th @ 10:00 am Pacific. ** Priorities 1. Puppet 3.7.1 2. CFacter on the march 3. New puppet doc implementation 4. Code removal for puppet 4 Commentary Sorry about being late on this, still getting back into the swing of things after vacation. Pu

Re: [Puppet-dev] Statistics for Modules

On Sun, Sep 7, 2014 at 3:57 PM, Spencer Krum wrote: > Hi Puppet-dev, > > I've been working, with a lot of help from some others, on a new project > at http://puppet-analytics.org. It is very much in the > experimental/development phase and I'm looking for feedback and help. > > The goal of this p

[Puppet-dev] Puppet 3.7 is out! Long live Puppet 4

For the past couple of months we've had a puppet-4 branch running which allowed us to land any breaking changes that should go into puppet 4.0 without having to hold onto them. Now that puppet 3.7.0 has been released, that opens up the master branch for puppet 4.0 development! Rejoice! Over the ne

Re: [Puppet-dev] Puppet Setting Deprecation

On Thu, Sep 4, 2014 at 1:05 PM, Joshua Partlow < joshua.part...@puppetlabs.com> wrote: > On Thu, Sep 4, 2014 at 12:34 PM, Nan Liu wrote: > >> Yes, I'm looking for the environment specific modulepath. >> >> Maybe this is a more complete example: >> example = Puppet::Module.find('example', Puppet[

Re: [Puppet-dev] Remove PSON document_type

On Wed, Sep 3, 2014 at 4:32 AM, Erik Dalén wrote: > It would be nice to remove the document_type from the PSON hashes for > Puppet 4. This would be a modification of the API though, so it is a > backwards incompatible change. But it is data that AFAIK the agent throws > away anyway when it receiv

Re: [Puppet-dev] Platform Team Week ending August 22nd, 2014

On Sun, Aug 24, 2014 at 4:54 PM, Kylo Ginsberg wrote: > ** Next PR Triage Wednesday, August 27th @ 10:00 am Pacific. ** > > Priorities > > 1. Puppet 3.7.0 with the final language polish as well as many other > changes. > 2. Windows stability improvements/x64 support > 3. Facter 2.2 > 4. C

Re: [Puppet-dev] Re: Feedback on the behavior of +=, -=, +, and -

information about what is going on (it isn't just a syntax error, it actually parses += and -= and says that they are no longer supported). > > On Mon, Aug 11, 2014 at 12:11 PM, Andy Parker wrote: > >> On Sun, Aug 10, 2014 at 10:53 PM, Reid Vandewiele >> wrote: >&

Re: [Puppet-dev] Re: Replacement for puppet doc

On Tue, Aug 12, 2014 at 10:19 AM, Hailee Kenney wrote: > > Thanks for all the feedback everyone! Going back to the issue of naming, I > have a list of suggestions I've collected that I wanted throw out there for > discussion: > > puppet strings (this seems to be a popular choice) > I like this o

Re: [Puppet-dev] Re: Syntax of resource expressions (was: Decision: Near future of resource expressions)

> > I think this is better because now all the logic of create_resources is > present here in the puppet code: the merging of defaults with specified > parameters AND the iteration. > > > Thanks, > Spencer > > > On Mon, Aug 11, 2014 at 6:58 PM, Henrik Lindberg

Re: [Puppet-dev] Syntax of resource expressions (was: Decision: Near future of resource expressions)

On Tue, Aug 5, 2014 at 11:25 PM, David Schmitt wrote: > Hi, > > thanks for keeping the ball rolling! > > > On 2014-08-06 02:51, Andy Parker wrote: > >> I'm pulling this discussion out into a new thread so that we can become >> more focussed. I'm also go

Re: [Puppet-dev] Re: Feedback on the behavior of +=, -=, +, and -

On Sun, Aug 10, 2014 at 10:53 PM, Reid Vandewiele wrote: > On Sunday, August 10, 2014 7:11:11 PM UTC-7, Trevor Vaughan wrote: >> >> Yeah, I know that it doesn't actually mutate. But it *feels* like it >> does, which is the issue. >> >> Trevor >> > > For this reason I would advocate omission of +=

[Puppet-dev] Platform Team Week of August 8th, 2014

** Next PR Triage Wednesday, August 13th @ 10:00 am Pacific. ** Priorities 1. Puppet 3.7.0/4.0.0 with the final language polish as well as many other changes. 2. Windows stability improvements/x64 support 3. CFacter on the march 4. New puppet doc implementation Commentary There was a bi

[Puppet-dev] Feedback on the behavior of +=, -=, +, and -

I'm looking over PUP-2972, which is closely related to PUP-489, and is specified (but changeable, hence this email!) at https://github.com/puppetlabs/puppet-specifications/blob/master/language/expressions.md#-operator-8 and https://github.com/puppetlabs/puppet-specifications/blob/master/language/ex

Re: [Puppet-dev] RFC: Static Analysis of the Puppet project

ct with `and` and `or`) > > Is there a preference here? > > On Fri, Aug 8, 2014 at 9:56 AM, Andy Parker wrote: > > On Thu, Aug 7, 2014 at 6:09 PM, Rahul Gopinath > wrote: > >> > >> While hacking rubocop, I found that I can get it to autocorrect eve

Re: [Puppet-dev] RFC: Static Analysis of the Puppet project

x27;t have one, so it falls back to the .rubocop.yml. If we > >> wanted to have a set of cops which triggered comments on the PRs, but > didn't > >> figure travis fails, we could get that by having a separate > houndci.yml. Not > >> sure what I think of that, but ju

[Puppet-dev] Iteration functions, which ones do we need?

It has been brought to my attention that there are a number of the functions that were added as part of the "iteration in the puppet language" work that there isn't any kind of general agreement on their value. I think the list of functions in question is: * map * reduce * filter * slice

[Puppet-dev] Syntax of resource expressions (was: Decision: Near future of resource expressions)

ere are we can definitely get some study done. On Tue, Aug 5, 2014 at 4:11 PM, Henrik Lindberg < henrik.lindb...@cloudsmith.com> wrote: > On 2014-05-08 18:24, Andy Parker wrote: > >> On Tue, Aug 5, 2014 at 8:18 AM, Erik Dalén > <mailto:erik.gustav.da...@gmail.com&g

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

On Tue, Aug 5, 2014 at 8:18 AM, Erik Dalén wrote: > On 5 August 2014 16:25, Reid Vandewiele wrote: > >> On Mon, Aug 4, 2014 at 3:18 PM, Henrik Lindberg < >> henrik.lindb...@cloudsmith.com> wrote: >> >>> >>> So, to summarize: The use of * => as an operator is not liked but the >>> concept of bein

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 >> <mailto:a...@p

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

On Fri, Aug 1, 2014 at 12:39 AM, David Schmitt wrote: > On 2014-07-31 22:16, John Bollinger wrote: > [good points] > > Just a quick note that I'm mainly agreeing with John's points: Automatic > (and inconsistent) stringification of non-string-titles is weird and > confusing, thus should be avoide

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

On Wed, Jul 30, 2014 at 1:02 PM, John Bollinger wrote: > On Tuesday, July 29, 2014 1:23:09 PM UTC-5, Andy Parker wrote: > >> On Thu, Jul 24, 2014 at 5:32 PM, Andy Parker >> wrote: >> >>> Howdy, >>> >>> Henrik, David, Erik, John, and others

Re: [Puppet-dev] RFC: Static Analysis of the Puppet project

On Tue, Jul 29, 2014 at 4:53 PM, Jeff McCune wrote: > On Tue, Jul 29, 2014 at 4:42 PM, Andy Parker wrote: > >> Here is an example >> https://github.com/puppetlabs/puppet/pull/2900/files#diff-f9ef6a029a765863382f55a75a8fbd7cR27 >> > > Could you help me understand wh

Re: [Puppet-dev] RFC: Static Analysis of the Puppet project

On Tue, Jul 29, 2014 at 4:17 PM, Rahul Gopinath wrote: > Andy, > > [...] > > Absolutely. I haven't looked at the full context of that statement, but > > there is likely something that is being guarded by the return value of > > execute_prerun_command, but the guard isn't made clear by the structu

Re: [Puppet-dev] RFC: Static Analysis of the Puppet project

On Tue, Jul 29, 2014 at 1:35 PM, Adrien Thebo wrote: > When reviewing pull request 2900 to add Rubocop and remove instances > And/Or, I came across some rather interesting behavior with how the boolean > operators interact with some keywords and methods. For the sake of clarity > I'm copying my c

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

On Tue, Jul 29, 2014 at 11:54 AM, Reid Vandewiele wrote: > Definitely excited to see this stuff moving forwards. > > On Thursday, July 24, 2014 5:32:13 PM UTC-7, Andy Parker wrote: > >> >> Henrik took all of the ideas and started trying to work out what we could >>

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

On Thu, Jul 24, 2014 at 5:32 PM, Andy Parker wrote: > Howdy, > > Henrik, David, Erik, John, and others have been having some pretty epic > conversations around resource expressions, precedence, order of evaluation, > and several other topics. What kicked all of that off was us loo

[Puppet-dev] Platform Team Week of July 21st, 2014

** Next PR Triage Wednesday, July 30th @ 10:00 am Pacific. ** Priorities 1. Puppet 3.7.0/4.0.0 with the final language polish as well as many other changes. 2. Windows stability improvements/x64 support 3. CFacter on the march Commentary The language work is nearing the end. The past week

Re: [Puppet-dev] rsepc example for testing file manipulation

Hi Johan, On Fri, Jul 25, 2014 at 5:08 AM, Johan De Wit wrote: > Hi, > > Does someone knows more rspec code examples for working with files ? > > I stumbled across https://github.com/puppetlabs/puppetlabs-inifile/blob/ > master/spec/unit/puppet/provider/ini_setting/ruby_spec.rb , > > but cannot

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

On Thu, Jul 24, 2014 at 6:04 PM, Henrik Lindberg < henrik.lindb...@cloudsmith.com> wrote: > On 2014-25-07 2:32, Andy Parker wrote: > >> >> >> DECISION SEVEN >> >>undef is not allowed as a title >> >> Not much to say here. notify {

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

Howdy, Henrik, David, Erik, John, and others have been having some pretty epic conversations around resource expressions, precedence, order of evaluation, and several other topics. What kicked all of that off was us looking for some feedback on decisions we were making for the Puppet 4 language ab

Re: [Puppet-dev] Metaparam Warning

On Mon, Jul 21, 2014 at 10:37 AM, Nan Liu wrote: > I'm using puppet-system module and the usage of the schedule metaparameter > is generating a large amount of warnings similar to the one below (about 30 > lines): > > Warning: schedule is a metaparam; this value will inherit to all contained > re

Re: [Puppet-dev] Re: RFC - Grammar quirks I want to remove...

On Fri, Jul 18, 2014 at 8:55 AM, Henrik Lindberg < henrik.lindb...@cloudsmith.com> wrote: > On 2014-18-07 17:42, Andy Parker wrote: > >> On Fri, Jul 18, 2014 at 12:47 AM, Peter Meier > <mailto:peter.me...@immerda.ch>> wrote: >> >> -BEGIN

Re: [Puppet-dev] RFC - Grammar quirks I want to remove...

On Fri, Jul 18, 2014 at 12:47 AM, Peter Meier wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Can we get rid of this, it is bad enough that all other keywords > > can be used (if, unless, case, class, define, etc. etc.) > > Couldn't we ban them as well? I think in most other "progr

Re: [Puppet-dev] RFC: Static Analysis of the Puppet project

On Tue, Jul 15, 2014 at 11:01 AM, rahul wrote: > [..snip..] > > >> and then there's been some discussion on the PR around these two cops: >>> >>> Style/AndOr >>> Lint/AssignmentInCondition >>> >>> Each of those two checks catch coding patterns which both are a source >>> of some bugs and, at the

Re: [Puppet-dev] RFC: Static Analysis of the Puppet project

On Mon, Jul 14, 2014 at 3:08 PM, Kylo Ginsberg wrote: > So now putting on my opinionated hat ;) > > On Mon, Jul 14, 2014 at 12:04 PM, Andy Parker wrote: > >> On Mon, Jul 14, 2014 at 10:56 AM, Kylo Ginsberg >> wrote: >> >>> For the build and test pipeline

Re: [Puppet-dev] RFC: Static Analysis of the Puppet project

On Mon, Jul 14, 2014 at 10:56 AM, Kylo Ginsberg wrote: > HI all, > > We'd like to start using static analysis against the puppet code base both > to catch certain classes of coding errors and to enforce best coding > practices. Those are laudable goals of course, but there is plenty of room > for

[Puppet-dev] Puppet PR Triage Notes 2014-07-09

Joined: Andy, Adrien, Whopper Candidates for merging: * Puppet/2779: (PUP-2802) add slot support for packages in portage.rb * Puppet/2770: Allow version and held states of a package to specified as separate properties * Hiera/198: Add YAML output format to CLI * Facter/722: (FACT-621) Add

[Puppet-dev] Puppet PR Triage for 2014-07-09 starting soon

Starting in about 10 minutes at http://links.puppetlabs.com/pr-triage -- Andrew Parker a...@puppetlabs.com Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at PuppetConf 2014 , September 22-24 in San Francisco* *Register by May 30th to take advantage

[Puppet-dev] Puppet PR Triage Notes 2014-07-02

Joined: Andy, JoshC, Adrien, Whopper, Ashley, Joachim Candidates for merging: * Puppet/2756: (PUP-1177) make sure ssh_known_hosts is not created with mode 0600 * Puppet/2779: (PUP-2802) add slot support for packages in portage.rb * Puppet/2770: Allow version and held states of a package to s

[Puppet-dev] PR triage for 2014-07-02

We'll be starting in about 15 minutes at http://links.puppetlabs.com/pr-triage -- Andrew Parker a...@puppetlabs.com Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at PuppetConf 2014 , September 22-24 in San Francisco* *Register by May 30th to take

[Puppet-dev] Puppet PR Triage Notes 2014-06-25

Joined: Andy, Adrien, Felix Candidates for merging: * Puppet/2637: Make puppet master compile honor configured logdest - Candidate, but we'd like to have the contributor fix it up first (saves us the time) * Puppet/2753: (PUP-2737) purge sshkeys with spaces in the title * Puppet/2756: (P

[Puppet-dev] PR triage for 2014-06-25 starting

Join us in the hangout at http://links.puppetlabs.com/pr-triage -- Andrew Parker a...@puppetlabs.com Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at PuppetConf 2014 , September 22-24 in San Francisco* *Register by May 30th to take advantage of th

Re: [Puppet-dev] Re: Platform Team Week of June 8th, 2014

On Wed, Jun 25, 2014 at 5:27 AM, Trevor Vaughan wrote: > Henrik, > > Just got done reading through this and it looks quite useful. > > I do have a common use case that I'd like to see incorporated if possible > though. > > I would like to have users be able to input either a String or an Array >

[Puppet-dev] Puppet PR Triage Notes 2014-06-18

Joined: Andy, Peter, Erik, Felix Candidates for merging: * Puppet/2624: (PUP-2511) Add parser function digest: uses digest_algorithm to hash, not strictly md5 * Puppet/2637: Make puppet master compile honor configured logdest - Candidate, but we'd like to have the contributor fix it up fir

[Puppet-dev] Puppet PR triage for 2014-06-18

The PR triage will be starting in about 15 minutes (10am Pacific time) at http://links.puppetlabs.com/pr-triage -- Andrew Parker a...@puppetlabs.com Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at PuppetConf 2014 , September 22-24 in San Francisc

Re: [Puppet-dev] Re: Speculative Syntax: Varargs & Matchers

On Thu, Jun 12, 2014 at 4:14 AM, Igor Galić wrote: > Henry, Andy, > > that all sounds very promising, and exciting! > I'm very much looking forward for that. > > I don't want to get your hopes up and then dash them, but beyond what is already implemented in the type system we have no plans to imp

Re: [Puppet-dev] Speculative Syntax: Varargs & Matchers

On Wed, Jun 11, 2014 at 6:27 AM, Igor Galić wrote: > > Hi folks, > > over the last couple of days I've been dabbling with the design > for a new module for Apache httpd: we use our own package & module > currently, which allows for multi-instance configurations, but are > trying to shift towards

[Puppet-dev] Pull request triage - 2014-05-28

Pull request triage - 2014-05-28 This triage time was spent trying to burn down the backlog of PRs where we had already made decisions on. We spent nearly the entire time just working on the final review, test, cleanup, and merge. No new PRs were covered. Joined: Charlie, Ethan, Jeremy, JoshC, Ky

[Puppet-dev] PR Triage for 2014-05-28 about to start

Join us at http://links.puppetlabs.com/pr-triage This time we are going to concentrate on just trying to get through the backlog of merge items. Probably less discussion than normal. -- Andrew Parker a...@puppetlabs.com Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at Puppe

Re: [Puppet-dev] Re: Data binding for defines

On Thu, May 15, 2014 at 10:24 PM, David Schmitt wrote: > Hi, > > > On 16.05.2014 02:17, Alessandro Franceschi wrote: > >> >> >> On Thursday, May 15, 2014 9:55:05 PM UTC+2, John Bollinger wrote: >> >> I am concerned about the impact. It is already somewhat costly for >> Puppet to evaluate

Re: [Puppet-dev] Data binding for defines

On Thu, May 15, 2014 at 7:46 AM, Alessandro Franceschi wrote: > Hallo everybody, > I've tried to look around in the group for past discussions about this > topic but haven't found any. > If this has been already debated , please forgive me and point me to the > right direction. > > I tried to fin

[Puppet-dev] Puppet PR triage for 2014-05-14 starting soon

Join us in a Google hangout at http://links.puppetlabs.com/pr-triage -- Andrew Parker a...@puppetlabs.com Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at PuppetConf 2014 , September 22-24 in San Francisco* *Register by May 30th to take advantage

Re: [Puppet-dev] Puppet Templates - RFC

On Mon, May 12, 2014 at 7:13 AM, Erik Dalén wrote: > Is there any syntax validation tool available for this? Will something > like "puppet parser validate --parser=future" just work on epp files? > > I'm looking for some equivalent to "erb -x file.erb | ruby -c". > > There isn't one as far as I kn

Re: [Puppet-dev] 'puppet cert list' .. where is @ca initialized?

On Wed, May 7, 2014 at 4:07 PM, Drew Fisher wrote: > Good afternoon! > > I'm trying to get RBAC working on Solaris 11.2 for Puppet 3.4.1. Namely, > I need to be able to list and sign waiting certificates as a non-root user > (but with elevated RBAC permissions). No matter what happens, I can no

Re: [Puppet-dev] Re: Environment Caching - RFC

On Wed, Apr 23, 2014 at 12:31 PM, John Bollinger wrote: > > > On Tuesday, April 22, 2014 8:19:57 PM UTC-5, henrik lindberg wrote: >> >> The problem with doing the manual cache invalidation is knowing which >> running instance of the master to talk to > > > > Why would you want to talk only to one?

Re: [Puppet-dev] Re: Environment Caching - RFC

On Thu, May 8, 2014 at 11:23 AM, Daniele Sluijters < daniele.sluijt...@gmail.com> wrote: > So 3.6.0-rc1 is out but the new caching mechanism seems pretty much > useless to me without a face or method to invalidate that cache (restarting > the Puppetmaster is not a good method unless there's some o

Re: [Puppet-dev] Announce: Puppet 3.6.0-RC1 available

It looks like there is going to be an RC2. We have a regression in the module tool (PUP-2484). On Tue, May 6, 2014 at 11:57 AM, Eric Sorenson wrote: > Puppet 3.6.0 is a backward-compatible features and fixes release in the > Puppet 3 series. The biggest things in this release are: > > *

Re: [Puppet-dev] Puppet thread safety

On Fri, May 2, 2014 at 1:27 PM, Vincent Miszczak wrote: > Hello, > > I'd like to do the following : > > *site.pp* > custom_function_that_changes_puppet_internal_variables() > hiera_include("classes") > custom_function_that_restores_puppet_internal_variables() > > I would be very careful about doi

[Puppet-dev] The source of the massive slowdown with directory environments

This is an explanation of the slowdowns that some people saw with 3.5.0/1 when directory environments were enabled. It also explains how we didn't notice it and some of the pains we've had to work through on the caching system that we put into place (and there has been ongoing discussion here) for

Re: [Puppet-dev] Re: Environment Caching - RFC

On Thu, May 1, 2014 at 11:24 AM, Joachim Thuau wrote: > > > On Tuesday, April 22, 2014 6:41:18 AM UTC-7, Trevor Vaughan wrote: >> >> The more I read all of this, the more I'm a fan of a MANUAL mode. >> >> Cool. I'm coming around to the viewpoint that we are going to have to support this, but it i

[Puppet-dev] Notes from Puppet PR Triage for 2014-04-30

Pull request triage - 2014-04-30 Joined: Andy, Charlie, Adrien, JoshC, Hunner, Kylo, Rob, PeterH, BrianLM Candidates for merging: - 2492: (PUP-1381) issue warnings to current users of cron purging - 2455: (PUP-2014) Make gem provider match on a single gem name - Needs a test added - 24

[Puppet-dev] Puppet PR Triage for 2014-04-30 starting

We'll be starting in about 10 minutes at http://links.puppetlabs.com/pr-triage This one will be a little quieter since we are working to get the 3.6.0 release out. -- Andrew Parker a...@puppetlabs.com Freenode: zaphod42 Twitter: @aparker42 Software Developer *Join us at PuppetConf 2014

Re: [Puppet-dev] Does hiera_include work properly with freeze_main?

I pretty sure we haven't tested that combination. Does freeze_main even do anything? On Tue, Apr 29, 2014 at 7:05 AM, Trevor Vaughan wrote: > I'm testing hiera_include with freeze_main enabled using 3.5.0-1 and I > suspect that they are not playing well together. > > Has this function combinati

Re: [Puppet-dev] Re: Environment Caching - RFC

On Mon, Apr 28, 2014 at 4:51 AM, Brice Figureau < brice-pup...@daysofwonder.com> wrote: > On Wed, 2014-04-23 at 03:19 +0200, Henrik Lindberg wrote: > > On 2014-22-04 8:06, Thomas Hallgren wrote: > > > Would a MANUAL strategy make sense? I.e. instead of rebooting the > > > master, just tell it to c

  1   2   3   4   5   >