[Puppet-dev] status of PRFC process?

I received marketing email this morning about "Puppet Application Orchestration". I'm guessing this is related to PRFC-6 and the recent PR's for PUP-s that are not publicly accessible. If this feature is indeed related to PRFC-6, the index page lists this PRFC as being in "draft" status. Per

Re: [Puppet-dev] Puppetconf 2015: pre-summit tea party

My flight is scheduled to arrive at 16:48. :/ I will attempt to drop by for the last few minutes. -Josh -- On 09/25/2015 10:12 AM, David Lutterkort wrote: > +1 .. sounds great, thanks for organizing. > > David > > On Mon, Sep 21, 2015 at 6:38 AM, Daniele Sluijters > mailto:daen...@spotify.com>> w

Re: [Puppet-dev] Docker module and new upstream repos

On 07/26/2015 09:31 AM, Gareth Rushgrove wrote: * Previously the module defaulted to upstream docker packages for Ubuntu, and used distro packages for everything else (because they didn't exist). I'm proposing to change this, so everything by default uses the upstream. And to document how you ca

Re: [Puppet-dev] Module Testing and Facter 3

I don't typically have system packages for either puppet or facter in my dev environment as I've had bazaar issues in the past where the system facter has leaked into the bundler env and cause odd test failures. Has anyone looked into embedding cfacter in a gem? Another implication, which is CI s

[Puppet-dev] puppet4 regressions or features?

As I'm slowly updating my modules' testing boilerplate for puppet 4.x, I've run into a couple cases of breakage that I'm unsure if they are intentional changes in semantics or regressions. When introspecting on a resource and the param is undefined, an empty string is now being returned instea

Re: [Puppet-dev] Re: Unit testing v4 functions in modules

The core v4 function unit tests appear to be using Puppet::Pops::Loaders to find the function method. E.g. Puppet.lookup(:loaders).puppet_system_loader.load(:function, 'regsubst').call({}, *args) From: https://github.com/puppetlabs/puppet/blob/master/spec/unit/functions/regsubst_spec.rb -J

[Puppet-dev] confining providers by lib

Last week I was investigating solutions for retrying IPC/RPC operations in a provider I'm working on and discovered that the puppetlabs-aws module does exactly what I was looking for with the retries gem. I believe the typical pattern for a provider to require a gem is to declare a new feature (for

Re: [Puppet-dev] catalog access from provider class methods?

e the method you want. https://github.com/branan/puppet-jenkins/blob/jenkins_agent_type/lib/puppet/provider/jenkins_agent/json.rb#L50 is my code from a few years ago. On Wed, Apr 15, 2015 at 10:58 AM, Joshua Hoblitt wrote: Hi Branna, Under 3.7.5, that gives me a Puppet::Indirector::Face object.

Re: [Puppet-dev] catalog access from provider class methods?

oading facts from /home/vagrant/jenkins/lib/facter/jenkins.rb Notice: Compiled catalog for foobar in environment production in 0.01 seconds => :foobar ? -Josh -- On 04/15/2015 10:58 AM, Joshua Hoblitt wrote: Hi Branna, Under 3.7.5, that gives me a Puppet::Indirector::Face object. htt

Re: [Puppet-dev] catalog access from provider class methods?

ill continue to work in the future. -- Branna On Tue, Apr 14, 2015 at 7:49 PM, Joshua hoblitt wrote: I desire the ability to access DSL class parameters from within a provider. Similar to the pattern that is frequently seen with DSL defined types and a controlling class within a module. AFAIK, t

Re: [Puppet-dev] catalog access from provider class methods?

On 04/14/2015 07:49 PM, Joshua hoblitt wrote: I desire the ability to access DSL class parameters from within a provider. Similar to the pattern that is frequently seen with DSL defined types and a controlling class within a module. AFAIK, the alternatives for sharing data are ugly. Including

[Puppet-dev] catalog access from provider class methods?

I desire the ability to access DSL class parameters from within a provider. Similar to the pattern that is frequently seen with DSL defined types and a controlling class within a module. AFAIK, the alternatives for sharing data are ugly. Including: forcing the user to declare facts via ENC o

Re: [Puppet-dev] Non-breaking changes and puppet 3.7.x

On 12/04/2014 02:24 PM, Kylo Ginsberg wrote: > ** non-breaking changes go to 3.7.x (and are merged up -> stable -> master) I suspect random bug fixes will be largely submitted as PRs against the 'stable' ref. That might mean a situation of having to back merge to 3.7.x and forward merge to master

Re: [Puppet-dev] rspec-puppet issues under Ruby 2

On 12/02/2014 10:28 AM, Jeff McCune wrote: > It's been a long time since the last release, so if anyone has been working > with the rspec-puppet "master" branch, please let me know if you've run > into backwards-compatibility issues in master that would motivate a 2.0.0 > release, or pulling out th

Re: [Puppet-dev] Puppet 4 delivery and upgrades

On 11/19/2014 12:36 PM, Eric Sorenson wrote: > If any one of the main constituent projects having a release would cause a > new AIO to come out, is that the right cycle? Yes, no, maybe, it depends? Is the proposed plan to roll out a new AIO if PL product versions are unchanged but a vendored prod

Re: [Puppet-dev] Puppet 4 delivery and upgrades

s will still be packaged, and > will be updated to use the new layout so they will be compatible with > the AIO package. > > The AIO model is the model that our windows packages have been using > for some time now with great success. > > On Wed, Nov 19, 2014 at 9:52 AM, Joshua H

Re: [Puppet-dev] Puppet 4 delivery and upgrades

On 11/18/2014 12:04 PM, Eric Sorenson wrote: > 3. The AIO packages will have a filesystem layout that installs the > programs into /opt/puppetlabs/agent and the configs into > /etc/puppetlabs/agent ; the packages will be a different basename than > puppet ('puppet-agent') so won't install automatic

Re: [Puppet-dev] Puppet 4 delivery and upgrades

On 11/18/2014 06:11 PM, Michael Stahnke wrote: > > On EL6.x, why not use a new SCL? Or even install into the existing > ruby193 SCL? > > > Part of the goal here is to have control of the ruby version. The SCL > offers one version of Ruby 1.9.3, Ubuntu offers another in their > distribution

Re: [Puppet-dev] Puppet 4 delivery and upgrades

On 11/18/2014 12:04 PM, Eric Sorenson wrote: > 2. To enable #1 but still support OSes that ship with 1.8.7, we're > going to be packaging and delivering Puppet 4 an an 'all-in-one' (AIO) > package bundled together with > - openssl > - ruby > - augeas > - ruby-augeas > - ruby-stomp > - ruby-s

Re: [Puppet-dev] zpool mirror and raidz virtual devices

On 11/11/2014 12:06 AM, Josh Cooper wrote: > Adam put together a PR > at > https://github.com/Incognito1992/puppet/compare/ticket/master/PUP-3388-zpool-mirrors > , > but while researching it, I think this is real

Re: [Puppet-dev] Improving the Resources Resource Type

On 11/06/2014 04:04 AM, Luke Kanies wrote: > A fourth option would be to combine the best of Resources and exported > resources: Build a querying system akin to exported resources, but > against the current system, rather than against the catalog. Or > really, take the exact same querying we alre

Re: [Puppet-dev] Setting log levels in puppet.conf

On 11/04/2014 11:53 PM, David Schmitt wrote: > > Commandline options should always trump config file settings for > reduced surprise factor. ^^^ This -Josh -- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group

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

On 11/04/2014 09:09 PM, Joshua Hoblitt wrote: > On 11/04/2014 01:04 PM, Andy Parker wrote: >> >> >> It would also provide at lot more confidence that a manifest is >> 4x safe >> if it passes `puppet parser validate`. Without that you'd have &g

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

On 11/04/2014 01:04 PM, Andy Parker wrote: > > > It would also provide at lot more confidence that a manifest is 4x > safe > if it passes `puppet parser validate`. Without that you'd have to > worry > about conditional expressions silently changing their result > between 3x

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

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. > > The bad part is that ==, != cannot raise errors (since a string i

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

On 11/02/2014 05:34 PM, Henrik Lindberg wrote: > On 2014-02-11 10:19, Joshua Hoblitt wrote: >> On 11/01/2014 03:35 AM, David Schmitt wrote: >>> On 2014-11-01 01:22, Henrik Lindberg wrote: >>> >>> The requirement to compare strings and numerals can also be >&

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

On 11/03/2014 02:09 AM, Thomas Hallgren wrote: >> >> (String)$my_hungarian_integer > I perceive this as a type cast, not a conversion, and would expect a > runtime exception unless $my_hungarian_integer already is a string. Welcome to the "magic" of C. The type casting syntax is both a way of exp

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

On 11/01/2014 03:35 AM, David Schmitt wrote: > On 2014-11-01 01:22, Henrik Lindberg wrote: > > The requirement to compare strings and numerals can also be > implemented by converting the numeral to a string (using a canoical > non-locale dependent format). This produces a much safer route, as > cre

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

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 breath at having to do so). (Yes, I could > probably query PuppetDB for t

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

On 10/23/2014 05:04 PM, Andy Parker wrote: > MessagePack might be nice. It is pretty well specified, has a fairly > large number of libraries written for it, but it doesn't do much to > help us solve the wild west of encoding in puppet. In MessagePack > there aren't really any enforcements of strin

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

It seems to me that there are two reoccurring basic themes in this thread of folks expressing either: * eagerness to push more data into hiera or * sentiment that hiera is already a performance bottleneck The first is language / design pattern issue while the later is an engineering problem.

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

On 05/15/2014 12:55 PM, John Bollinger wrote: > > On Thursday, May 15, 2014 9:46:40 AM UTC-5, Alessandro Franceschi wrote: >> > >> > I wonder what do you thing about a feature request to have data bindings >> > also for defines' parameters. >> > > > I'm skeptical about their value. We already h

Re: [Puppet-dev] Puppet Heredoc for Puppet 3.5.0 - RFC

On 04/16/2014 01:05 PM, Andy Parker wrote: > On Tue, Apr 15, 2014 at 11:15 AM, Joshua Hoblitt wrote: >> >> * Is it possible to escape the endtag so that it can appear inside the >> heredoc string? >> >> > I don't believe so. In fact I don't know of an

Re: [Puppet-dev] Puppet Templates - RFC

On 04/16/2014 11:53 AM, Andy Parker wrote: > I am considering Joshua's request for the concat function. It would provide > a way to emit text from within the embedded code in the template, and might > help in some situations. But it another case where it adds a bit of special > stuff to do somethin

Re: [Puppet-dev] Puppet Templates - RFC

#x27;foo' > end > > output << 'bar' > -%> > <%= output.join("\n") %> > > > On Tue, Apr 15, 2014 at 2:38 PM, Joshua Hoblitt wrote: > >> I see the "Non Goals" section at the top of the arm but... >> >> The biggest fru

Re: [Puppet-dev] Puppet Templates - RFC

On 04/15/2014 12:28 PM, John Bollinger wrote: > > You are complaining about a problem partially of your own making: you break > up the Ruby a lot more than you need to do. Obviously you *can* do it like > that, but why? I find it's difficult to comprehend nested code intermixed with lines that

Re: [Puppet-dev] Puppet Templates - RFC

I see the "Non Goals" section at the top of the arm but... The biggest frustration I have with ERB is when you end up needing nested flow control logic. As example, to walk through a hash/array/etc. nested inside some conditional logic. The result is an eye gouging mix of nested <% ... %> and <%

Re: [Puppet-dev] Puppet Heredoc for Puppet 3.5.0 - RFC

I haven't tried it (I just started testing 3.5.1-rc1 this morning) so these are quick comments from only having looked at the ARM. * I really like the perl5 style interpolation control. * The End Marker/indentation control is a great feature. * Is it possible to escape the endtag so that it can

Re: [Puppet-dev] Constraints

On 04/15/2014 10:38 AM, Andy Parker wrote: > Generate might the appropriate place, or some new hook that we don't have > yet. There has been a constant need for lifecycle hooks so that providers > can make better decisions. +1 This is a tad tangential but I occasionally fantasize about a mount pr

Re: [Puppet-dev] Platform Team Week of January 27th, 2013

On 02/03/2014 10:56 AM, Andy Parker wrote: > > Trying out some different data this time. With the change to not having > Adrien dedicated to handling contributions I'm going to start publishing > a snapshot of the pull request metrics so that we can see if there are > any unwanted consequences. >

[Puppet-dev] Re: [Puppet Users] request for /proc/cpuinfo examples from aix, hpux, kfreebsd, & non-x86 linux

It's been a week and I haven't gotten a single response. Does anyone actually use those platforms? :) -Josh -- On 10/13/2013 02:41 PM, Joshua Hoblitt wrote: > Hi Folks, > > I'm looking at tidying up the way /proc/cpuinfo is parsed in facter and > the in tree fixt

[Puppet-dev] request for /proc/cpuinfo examples from aix, hpux, kfreebsd, & non-x86 linux

Hi Folks, I'm looking at tidying up the way /proc/cpuinfo is parsed in facter and the in tree fixture examples for any kernel other than linux i386/amd64 are pretty sparse. This is makes refactoring hairy as there are regexps and other assumptions baked into the code for these formats without any

Re: [Puppet-dev] The future of known_resource_types and loading puppet manifests

On 08/26/2013 11:41 AM, Andy Parker wrote: > How would you handle reloading in this scenario? > > > I can think of two ways: track all of the files loaded and reload when > something changes or is added, reload only when told. I lean towards the > "reload only when told" for a production mast