Re: [Puppet-dev] was - Idea: Deprecation logs

Fantastic response, Eric, couldn't have (and obviously didn't) said it better myself. > On Apr 28, 2016, at 8:00 PM, Eric Sorenson wrote: > > >> On Apr 11, 2016, at 9:17 AM, Alex Harvey wrote: >> >> An example might be abstract data types. I know that the data types had >> issues, oddities

Re: [Puppet-dev] Re: The Future of Puppet [Was: Deprecation logs]

On Apr 13, 2016, at 1:48 AM, Andreas Zuber wrote: > > > > On 04/11/2016 07:38 PM, R.I.Pienaar wrote: >> >> >> On 11 Apr 2016, at 17:45, Eric Shamow < >> eric.sha...@gmail.com >> > wrote: >> >>> On April 11, 2016 at 4:08:51 AM, R.I

Re: [Puppet-dev] Re: The Future of Puppet [Was: Deprecation logs]

On Apr 12, 2016, at 10:54 AM, Dean Wilson wrote: > > On 11 April 2016 at 12:08, R.I.Pienaar wrote: > >> Eric asked so here it is, this is my feedback with a open source user hat >> on. Echoing much what was said. I hope others send in their story. > > Since you asked so politely. > > I have

Re: [Puppet-dev] The Future of Puppet [Was: Deprecation logs]

On Apr 11, 2016, at 4:08 AM, R.I.Pienaar wrote: > - Original Message - >> From: "Thomas Gelf" >> To: "puppet-dev" >> Sent: Monday, 11 April, 2016 03:30:58 >> Subject: [Puppet-dev] Re: The Future of Puppet [Was: Deprecation logs] > >> Am 11.04.2016 um 03:01 schrieb Rob Nelson: >>> Of cou

Re: [Puppet-dev] metaparam question

> On Feb 4, 2016, at 3:35 PM, Kylo Ginsberg wrote: > >> On Wed, Feb 3, 2016 at 7:47 AM, R.I.Pienaar wrote: >> hello, >> >> I would like to add a metaparameter - which I think is easy now via >> Type.newmetaparam. > > We haven't been thinking of metaparameters as a general purpose extension >

Re: [Puppet-dev] Trying to consolidate/batch command execution in a provider

We’ve tried multiple times to build something to support this within the RAL, but we’ve never been able to come up with something sufficiently robust. We do have ‘prefetch’ for combining discovery commands, but nothing for combining the execution of the commands, AFAIK. On Jan 27, 2016, at 1:0

Re: [Puppet-dev] implementation of faces

On Sep 23, 2015, at 1:30 AM, Erik Dalén wrote: > > > > On Tue, 22 Sep 2015 at 20:43 Reid Vandewiele <mailto:r...@puppetlabs.com>> wrote: > On Tuesday, September 22, 2015 at 9:17:22 AM UTC-7, Luke Kanies wrote: > On Sep 21, 2015, at 7:52 PM, Corey Osman > wr

Re: [Puppet-dev] implementation of faces

On Sep 21, 2015, at 7:52 PM, Corey Osman wrote: > > Hi, > > I remember when the puppet 2.7 release came out with support for faces was > all the rage. The faces API seemed pretty slick as its a pluggable system > that allows the plugin to implement options as well. I am curious if there > i

Re: [Puppet-dev] Use catalogs from PuppetDB

On Thu, Jul 2, 2015 at 5:19 AM, Ken Barber wrote: > > I've been trying to use the catalogs stored in the PuppetDB to make the > > puppet-catalog-diff tool faster (instead of recompiling). > > > > However, the catalogs are munged before being stored in the PuppetDB, so > > this does not work. > >

Re: [Puppet-dev] Caching catalogs

On Jun 29, 2015, at 8:43 AM, Raphaël Pinson wrote: > > Hello, > > > I've activated caching on our Puppetservers, using the admin API to > invalidate the cache upon deploying new environments. However, this only > caches manifests, and catalogs still need to be compiled for every request. >

Re: [Puppet-dev] Validation Resources

On May 14, 2015, at 12:11 PM, Spencer Krum wrote: > > Hi Folks, > > There is currently a PR against stdlib that I am writing to you today > about: https://github.com/puppetlabs/puppetlabs-stdlib/pull/444 > Thanks to Spredzy for making this PR. > > This is tracked in jira: > https://tickets.pupp

Re: [Puppet-dev] Validation Resources

On May 14, 2015, at 4:00 PM, Erik Dalén wrote: > > > > On Thu, 14 May 2015 at 21:45 Trevor Vaughan > wrote: > Hmmwhat about a concept of deferred actions? > > I.e. Try this resource, can't do it, shove it (and it's dependencies) to the > bottom of the stack

Re: [Puppet-dev] Extending the File Type to allow setting an (Amazon Web Services) s3:/// URI

FWIW - I love that you’re adding this, people have been asking for this kind of thing for years, and I agree it’s much cleaner and better to have it in the core type. > On Jan 22, 2015, at 4:44 AM, Felix Frank > wrote: > > Hi, > > I'm working on a similar feature request in order to support

Re: [Puppet-dev] Accessing puppet catalog in provider self.* methods

On Jan 30, 2015, at 1:37 AM, Nan Liu wrote: > > I'm trying to use ini_setting as a parent provider. Everything works well, > but to support purging, the resources provider need to specify the target > file via self.file_path. Initially this seems straightforward, but the config > file location

Re: [Puppet-dev] puppet-dev status week ending 2014-12-05

On Dec 4, 2014, at 3:44 PM, Kylo Ginsberg wrote: PR Triage Schedule notes: - No PR Triage Wednesday, December 10th (PL has a company meeting) - Next PR Triage Wednesday, December 17th @ 10:00 am Pacific. Priorities 1. Puppet 4.0 (and 3.7.4) 2. Native Facter 0.3.0

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

On Nov 6, 2014, at 10:38 PM, Felix Frank wrote: > On 11/06/2014 12:04 PM, 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, ra

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

On Nov 7, 2014, at 2:02 PM, Joshua Hoblitt wrote: > 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, ra

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

On Thu, Nov 6, 2014 at 1:36 PM, Henrik Lindberg < henrik.lindb...@cloudsmith.com> wrote: > Hi, > I am bringing up this topic because of a recent discussion and PR for the > ticket https://tickets.puppetlabs.com/browse/PUP-1486 > > Here is a recap. > > The Resources resource is used to "manage unma

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

> On Oct 26, 2014, at 12:08 AM, James Turnbull wrote: > > Andy Parker wrote: >> the communication was done with PSON, which is a variant of JSON that >> has been in use in puppet since at least 2010. As far as I understand >> PSON started out as simply a vendored version of json_pure. The name >>

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

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, Andy Parker wrote: > A while ago we removed support for puppet to *send* YAML on the network. > At the same time we

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

On Oct 14, 2014, at 9:42 AM, Erik Dalén wrote: > > On 14 October 2014 01:13, Charlie Sharpsteen wrote: > > On Thursday, October 9, 2014 3:10:55 PM UTC-7, John Bollinger wrote: > > > On Thursday, October 9, 2014 9:12:41 AM UTC-5, Felix Frank wrote: > So in response to Andy's request for a pic

Re: [Puppet-dev] Re: Lightweight PuppetDB replacement

On Sep 15, 2014, at 5:57 PM, Jason Antman wrote: > If this was just a troll, I'll speak the unfortunate truth - please keep that > on the puppet-users list, which is increasingly filling with it. Hi Jason, That's the first I've heard anyone say that puppet-users is filling with trolls. I'd

Re: [Puppet-dev] Lightweight PuppetDB replacement

> On Sep 8, 2014, at 6:44 AM, Bomber wrote: > > Is any plans to implement lightweight puppetdb replacement for storeconfigs? > PuppetDB is ugly, i.e. has junkie API and _very_ heavy by itself because of > JVM, henve it is almost impossible to use it for testing masterless > environments, old ac

Re: [Puppet-dev] Remove PSON document_type

On Sep 3, 2014, at 11:00 AM, Andy Parker wrote: > 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

Re: [Puppet-dev] A question about numbers and representation

On Sep 1, 2014, at 1:54 AM, Henrik Lindberg wrote: > Hi, > Recently I have been looking into serialization of various kinds, and the > issue of how we represent and serialize/deserialize numbers have come up. > > TL;DR - I want to specify the max values of integers and floats in the puppet >

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

> On Aug 12, 2014, at 3:51 PM, Henrik Lindberg > wrote: > >> On 2014-12-08 19:47, Luke Kanies wrote: >> On Aug 5, 2014, at 6:41 PM, Reid Vandewiele > <mailto:r...@puppetlabs.com>> wrote: >> >>> Visual review, for convenience: >>>

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

> On Aug 12, 2014, at 3:07 PM, Henrik Lindberg > wrote: > >> On 2014-12-08 22:02, Spencer Krum wrote: >> >> >> 1) I really don't want to see variable expansion in >>expressions that >> resolve to the names of types. This will be misused, it >>will make code

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

On Aug 12, 2014, at 10:02 AM, Andy Parker wrote: > On Mon, Aug 11, 2014 at 8:54 PM, Spencer Krum wrote: > 1) I really don't want to see variable expansion in expressions that resolve > to the names of types. This will be misused, it will make code unreadable. > Please leave it out. Sets of par

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

On Aug 5, 2014, at 6:41 PM, Reid Vandewiele wrote: > Visual review, for convenience: > > file { $title: * => $attributes; } > file { $title: => $attributes; } > file { $title: ($attributes); } > file { $title: attribute_defaults => $attributes; } > file { $title: attribute_hash => $attributes; }

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

On Jul 30, 2014, at 1:02 PM, John Bollinger wrote: [...] > Here are the tests for the future parser (as changed by the PR) > > ["thing" ,"resource", ["thing"]], > ["[thing]","resource", ["thing"]], > ["[[nested, array]]" ,"resource", ["nested", "array"]

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

On Jul 28, 2014, at 7:33 AM, Henrik Lindberg wrote: > On 2014-28-07 8:34, Luke Kanies wrote: >> On Jul 24, 2014, at 5:32 PM, Andy Parker > <mailto:a...@puppetlabs.com>> wrote: >> >>> Howdy, >>> >>> Henrik, David, Erik, John, and othe

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

On Jul 28, 2014, at 6:43 AM, John Bollinger wrote: > > > On Friday, July 25, 2014 5:15:30 PM UTC-5, henrik lindberg wrote: > > We reasoned that we already have create_resources in frequent use to > solve real issues, so it is needed. I don't think create_resources is > used simply because yo

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

On Aug 1, 2014, at 9:28 AM, Andy Parker wrote: > > > > 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-

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

On 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 looking for some >

Re: [Puppet-dev] Saving graphs from puppet-catalog-test runs?

On Apr 22, 2014, at 12:49 PM, Matt Wise wrote: When we run our puppet-catalog-test runs ( https://github.com/invadersmustdie/puppet-catalog-test), we'd like to generate and save the .dot graph files so that we can turn them into images. I don;t know enough about the internal workings of Ruby/Pupp

Re: [Puppet-dev] Cfgmgmt: ParsedFile vs Augeas discussion

On Feb 5, 2014, at 8:52 PM, Ashley Penney wrote: On Wed, Feb 5, 2014 at 2:20 PM, Felix Frank wrote: > > > This resembles my feeling quite accurately. I've butted heads with > parsedfile quite a bit as well, and it can make you sad. > > Can you elaborate on the possible compatibility concerns? I

Re: [Puppet-dev] Puppet Custom Types, the easy way

From: John Bollinger John Bollinger Reply: puppet-dev@googlegroups.com puppet-dev@googlegroups.com Date: February 3, 2014 at 4:04:57 PM To: puppet-dev@googlegroups.com puppet-dev@googlegroups.com Subject:  Re: [Puppet-dev] Puppet Custom Types, the easy way On Saturday, February 1, 2014 7:48:53

Re: [Puppet-dev] Puppet Custom Types, the easy way

From: bert hajee bert hajee Reply: puppet-dev@googlegroups.com puppet-dev@googlegroups.com Date: January 28, 2014 at 10:44:42 PM To: puppet-dev@googlegroups.com puppet-dev@googlegroups.com Subject:  Re: [Puppet-dev] Puppet Custom Types, the easy way Just reread my reaction. Maybe it's not clear w

Re: [Puppet-dev] Puppet Custom Types, the easy way

From: bert hajee bert hajee Reply: puppet-dev@googlegroups.com puppet-dev@googlegroups.com Date: January 26, 2014 at 10:27:04 AM To: puppet-dev@googlegroups.com puppet-dev@googlegroups.com Subject:  [Puppet-dev] Puppet Custom Types, the easy way We have written a library to make it easier to buil

Re: [Puppet-dev] Pattern question for providers

On December 12, 2013 at 6:31:45 AM, Jeff Bachtel (jbach...@bericotechnologies.com) wrote: (repost from puppet-users)  When creating a provider that uses a command not in PATH, what is the  best-practice pattern for case'ing out different potential locations? As  an example, the puppetlabs rabbitm

Re: [Puppet-dev] Re: Puppet & out_of_sync_resources

Yep, that’s what it was meant to mean in the first place. From: Eric Sorenson Eric Sorenson Reply: puppet-dev@googlegroups.com puppet-dev@googlegroups.com Date: November 1, 2013 at 3:26:49 PM To: puppet-dev@googlegroups.com puppet-dev@googlegroups.com Subject:  [Puppet-dev] Re: Puppet & out_of_syn

Re: [Puppet-dev] Ideas for Batch Processing of Packages

On Oct 15, 2013, at 1:58 PM, Patrick Carlisle wrote: > > On Tue, Oct 15, 2013 at 1:50 PM, Nick Lewis wrote: >> If, in the course of implementing this, you happen to find it easy to >> implement an easy way to delay resources that might not be "ready", that >> would be awesome, too. That is,

Re: [Puppet-dev] Ideas for Batch Processing of Packages

That sounds awesome, Kylo. If, in the course of implementing this, you happen to find it easy to implement an easy way to delay resources that might not be "ready", that would be awesome, too. That is, if there were a hook similar to those below that could be used to see if a resource is ready

Re: [Puppet-dev] Idea around warnings and containment

On Sep 27, 2013, at 2:31 PM, John Bollinger wrote: > > > On Thursday, September 26, 2013 2:39:19 PM UTC-5, Luke Kanies wrote: > Do we have agreement that it's a good idea to find a way to encourage users > to provide more dependencies, and that it would be good if we cou

Re: [Puppet-dev] Idea around warnings and containment

On Sep 23, 2013, at 4:46 PM, John Bollinger wrote: On Sunday, September 22, 2013 5:22:10 PM UTC-5, Luke Kanies wrote: > > > On Sep 19, 2013, at 11:35 AM, John Bollinger > > > wrote: > > On Tuesday, September 17, 2013 1:36:34 PM UTC-5, Luke Kanies wrote: > > If I

Re: [Puppet-dev] Plugin sync support for external facts

On Sep 26, 2013, at 2:44 PM, Ryan Coleman wrote: On Thu, Sep 26, 2013 at 6:45 AM, Andy Parker wrote: > Agreed, the last thing that is needed is to present a solution that we say > is to make things "easier" and then have people start the simple case by > having to learn an abstract language ex

Re: [Puppet-dev] Plugin sync support for external facts

On Sep 26, 2013, at 2:44 PM, Ryan Coleman wrote: On Thu, Sep 26, 2013 at 6:45 AM, Andy Parker wrote: > Agreed, the last thing that is needed is to present a solution that we say > is to make things "easier" and then have people start the simple case by > having to learn an abstract language ex

Re: [Puppet-dev] Idea around warnings and containment

On Sep 19, 2013, at 11:35 AM, John Bollinger wrote: > > > On Tuesday, September 17, 2013 1:36:34 PM UTC-5, Luke Kanies wrote: > On Sep 12, 2013, at 1:15 PM, John Bollinger wrote: > >> >> >> On Wednesday, September 11, 2013 3:14:41 PM UTC-5, Luke Kanies wr

Re: [Puppet-dev] Idea around warnings and containment

On Sep 12, 2013, at 1:15 PM, John Bollinger wrote: > > > On Wednesday, September 11, 2013 3:14:41 PM UTC-5, Luke Kanies wrote: > On Sep 11, 2013, at 12:32 PM, John Bollinger wrote: > >> >> >> On Wednesday, September 11, 2013 11:58:55 AM UTC-5, Trevor Vaugha

Re: [Puppet-dev] Re: Ideas for Batch Processing of Packages

On Sep 15, 2013, at 8:55 PM, Henrik Lindberg wrote: > On 2013-16-09 5:41, Luke Kanies wrote: >> Hi Henrik, >> >> I know we have some users who just batch all package installs up front. >> It'd be interesting to see if that was a feasible solution. it woul

Re: [Puppet-dev] Ideas for Batch Processing of Packages

; group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-dev@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-dev. > For more options

Re: [Puppet-dev] Idea around warnings and containment

s to how one would disable those behaviors, I guess we'd have to introduce another function or a pragma or something. That might not be worth it. -- Luke Kanies | http://about.me/lak | http://puppetlabs.com/ | +1-615-594-8199 -- You received this message because you are subscribed to the Google Gr

Re: [Puppet-dev] Idea around warnings and containment

If you call warnings 'yelling', then yes, although we should probably allow those warnings to be turned off for the first release or so. -- Luke Kanies | +1-615-594-8199 | http://about.me/lak On Sep 11, 2013, at 9:58 AM, Trevor Vaughan wrote: This definitely works with the best p

[Puppet-dev] Idea around warnings and containment

Thinking about this this morning, how about: * we don't warn if Node is used to 'include' instead of containing classes * we don't warn when classes created by the ENC aren't contained * with that, I *think* we can warn when any other class is not contained. Right?

Re: [Puppet-dev] Re: Puppet 4 discussions

On Sep 3, 2013, at 1:46 PM, Andy Parker wrote: > On Tue, Sep 3, 2013 at 12:53 PM, Luke Kanies wrote: > On Sep 3, 2013, at 12:06 PM, Andy Parker wrote: > >> On Tue, Sep 3, 2013 at 11:34 AM, Drew Blessing >> wrote: >> I've been following this discussion for s

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

On Sep 5, 2013, at 2:31 PM, Jeff McCune wrote: > On Tue, Sep 3, 2013 at 12:44 PM, Luke Kanies wrote: >> +1 to a function expressing containment but not declaring the class (#3). >> It's the only option of the 4 provided that doesn't have the side-effect of >>

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

On Sep 4, 2013, at 5:22 PM, Eric Sorenson wrote: > On Sep 3, 2013, at 12:47 PM, Luke Kanies wrote: > >> It looks like we shouldn't need to touch the catalog stuff at all to make >> this work, so I agree. Is there a ticket out there for the catalog format >>

Re: [Puppet-dev] Re: Puppet 4 discussions

lso brought up another alternative > for creating a new container kind (module {} or something like that). I think > that would be another good avenue to explore. How difficult would it be to build tools to help our users understand when they might be making a mistake in this area? That is

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

ple, optional, backward-compatible fix. > Basically, if you're using the anchor pattern now, you can use the contain > function instead, and properly represents what's going on. > > +1 How is it that we're coming to the same decision as we did a year ago, everyone s

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

ain over time. A contains() > function allows the behavior to work with all the ways of adding classes to > the catalog while allowing us to maintain the code in one supported manner. Can you elaborate? I don't know what you mean. What's burdensome about having 'cont

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

al way for a normal user to see relationships, which resulted in whits being exposed. Along with other issues. So it was not just an implementation issue, it was a user experience issue. Which is why I care. -- Luke Kanies | http://about.me/lak | http://puppetlabs.com/ | +1-615-594-8199 --

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

On Aug 30, 2013, at 4:35 PM, Nick Lewis wrote: > On Friday, August 30, 2013 at 3:58 PM, Luke Kanies wrote: >> On Aug 30, 2013, at 10:47 AM, Andy Parker wrote: >> >>> On Fri, Aug 30, 2013 at 10:24 AM, Luke Kanies wrote: >>> On Aug 30, 2013, at 9:11 AM, And

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

On Aug 30, 2013, at 4:33 PM, Patrick Carlisle wrote: > > On Fri, Aug 30, 2013 at 3:58 PM, Luke Kanies wrote > Hmm. I'm essentially positive that there was a version of this bug that was > caused by whits cancelling out when classes were empty, but it sounds like > that

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

On Sep 1, 2013, at 11:32 AM, "Dustin J. Mitchell" wrote: > On Wed, Aug 28, 2013 at 1:20 PM, Luke Kanies wrote: >> That implies that we can't ship it until 4.0, which would be a tragedy >> worth fighting hard to avoid. > > At the risk of sounding imper

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

On Aug 30, 2013, at 10:47 AM, Andy Parker wrote: > On Fri, Aug 30, 2013 at 10:24 AM, Luke Kanies wrote: > On Aug 30, 2013, at 9:11 AM, Andy Parker wrote: > >> On Fri, Aug 30, 2013 at 1:05 AM, R.I.Pienaar wrote: >> >> >> - Original Message - >>

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

On Aug 30, 2013, at 1:05 AM, "R.I.Pienaar" wrote: > > > - Original Message ----- >> From: "Luke Kanies" >> To: puppet-dev@googlegroups.com >> Sent: Thursday, August 29, 2013 11:27:00 PM >> Subject: Re: Anchor pattern (was Re: [Puppet-

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

dev] Puppet 4 discussions) >> >> On 30 August 2013 09:55, Luke Kanies wrote: >> >>> On Aug 30, 2013, at 1:05 AM, "R.I.Pienaar" wrote: >>> >>>> >>>> >>>> - Original Message - >>>>> From: "

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

On Aug 30, 2013, at 9:11 AM, Andy Parker wrote: > On Fri, Aug 30, 2013 at 1:05 AM, R.I.Pienaar wrote: > > > - Original Message - > > From: "Luke Kanies" > > To: puppet-dev@googlegroups.com > > Sent: Thursday, August 29, 2013 11:27:00 PM

Re: [Puppet-dev] Re: Puppet 4 - Language revisions

On Aug 28, 2013, at 12:09 PM, Henrik Lindberg wrote: > On 2013-28-08 19:18, Luke Kanies wrote: >> On Aug 28, 2013, at 9:05 AM, Ryan Coleman > <mailto:r...@puppetlabs.com>> wrote: >> >>> >>> On Wed, Aug 28, 2013 at 8:04 AM, Henrik Lindberg >>

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

On Aug 29, 2013, at 12:24 PM, John Bollinger wrote: > > > On Wednesday, August 28, 2013 5:56:45 PM UTC-5, Andy Parker wrote: > On Wed, Aug 28, 2013 at 3:22 PM, Luke Kanies wrote: > On Aug 28, 2013, at 12:38 PM, Andy Parker wrote: >> On Wed, Aug 28, 2013 at 10:20 AM, Luke

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

of historical note: class inclusion used to result in containment the first time but not subsequent calls. I changed this behavior around 2.6 or so, because I couldn't find any good reasons for it and it made things much more complicated. I believe zero people noticed the change.) -- Luke K

Re: Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

On Aug 28, 2013, at 12:38 PM, Andy Parker wrote: > On Wed, Aug 28, 2013 at 10:20 AM, Luke Kanies wrote: > On Aug 28, 2013, at 8:45 AM, Andy Parker wrote: > > > * #8040 - anchor pattern. I think a solution is in sight, but it didn't > > make 3.3.0 and it i

Anchor pattern (was Re: [Puppet-dev] Puppet 4 discussions)

On Aug 28, 2013, at 8:45 AM, Andy Parker wrote: > * #8040 - anchor pattern. I think a solution is in sight, but it didn't > make 3.3.0 and it is looking like it might be backwards incompatible. Why would it be incompatible? That implies that we can't ship it until 4.0, which would be a trage

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

On Aug 28, 2013, at 7:06 AM, Henrik Lindberg wrote: [...] > To me, the problem we are discussing is that "autoloading" performs > evaluation of an unlinked model. The result therefore depends on the > transitive dependency graph of resolved links. We cache the result and then > try to figure ou

Re: [Puppet-dev] Puppet 4 - Language revisions

On Aug 28, 2013, at 9:05 AM, Ryan Coleman wrote: On Wed, Aug 28, 2013 at 8:04 AM, Henrik Lindberg < henrik.lindb...@cloudsmith.com> wrote: > Questions > = > * Do you think it is of value to have a "R3" language revision in Puppet 4? > Would the language changes correspond to major.mino

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

On Aug 26, 2013, at 2:47 PM, Ashley Penney wrote: On Mon, Aug 26, 2013 at 5:04 PM, markus wrote: > > > > > I think the system needs to change to eager loading of manifests > > > (not applying them all, but at least loading them all). > > Eager loading all manifests (e.g. by a directory search)

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

is impossible, or that the implementation of lazy loading is the problem? I could easily see the latter. How would you handle reloading in this scenario? Do you have a sense for what the performance difference would be for someone using Puppet interactively, especially with a smaller config set (i.

Re: [Puppet-dev] Manifest ordering of resources

On Aug 15, 2013, at 10:32 AM, Jeff McCune wrote: > On Thu, Aug 15, 2013 at 9:45 AM, Luke Kanies wrote: > On Aug 15, 2013, at 9:40 AM, Jeff McCune wrote: > >> On Wed, Aug 14, 2013 at 3:25 PM, Andy Parker wrote: >> >> Are we making any effort to help ensure end us

Re: [Puppet-dev] Manifest ordering of resources

provide a stable ordering of manifest files, regardless of > the parse-order they were included, while also providing the parse ordering > of resources within a class? What is the goal of that? -- Luke Kanies | http://about.me/lak | http://puppetlabs.com/ | +1-615-594-8199 Join us at PuppetCon

Re: [Puppet-dev] Re: Stop the new-hotness cycle..

e or anything like that, then evaluate the class. Then, in addition, throw an error (or maybe warning?) any time someone tries to override a class that's already been evaluated. And, in fact, I'd start with that second thing - start throwing warnings right now, and as quickly as poss

Re: [Puppet-dev] Selectively noop-ing resources based on the presence of other catalog resources.

tify' allowing for passing values through to the actual applied providers. However, I fear that this may lead to bouts of over-creativity and complexity if not used carefully. Thanks, Trevor On Mon, Jul 29, 2013 at 12:22 AM, Luke Kanies wrote: > Trevor Vaughan wrote: > >> Ok,

Re: [Puppet-dev] global resource flush?

d that is that in most cases you don't know when a given resource will actually be needed. E.g., you might have a Host, then a Service, then a Host, then another Service. If you just flushed Host at the end, then that first service (and, in fact, the second) might not work. Does your use

Re: [Puppet-dev] Selectively noop-ing resources based on the presence of other catalog resources.

whole-file methods and the per-record methods. I know that's not a great short-term fix, and I do think it's past time we added some kind of catalog control like this into the system. -- Luke Kanies | http://about.me/lak | http://puppetlabs.com/ | +1-615-594-8199 -- You receiv

Re: [Puppet-dev] Just a little fun on a Tuesday

t; } > > class { "bar": } Hmm. I'll make a go. (Note that I've been drinking at our OSCON party, so…) 5647123 I'm assuming that the brainteaster part is that the definitions are lazy evaluated but the classes aren't. -- Luke Kanies | http://about.me/

Re: [Puppet-dev] about the future parser

om the other hard work being done. I agree that the core sustaining engineering work is critical, but we do actually have users asking for new features all the time, and we can't ignore them or we'll look up in three years and everyone will be using SaltStack or Ansible. We'

Re: [Puppet-dev] Need the applied classes in a provider

> email to puppet-dev+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-dev@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-dev. > For more options, visit https://groups.google.com/groups/opt_out. > > -- Luke Kanies

Re: [Puppet-dev] Title vs namevar

On Apr 29, 2013, at 2:39 PM, Stefan Schulte wrote: > I'm currently trying to resolve issues around composite namevars but > there is one thing I do not understand: > > 1) It is common practice to ommit the namevar when declaring a resource > in a puppet manifest, because it is implicitly set by t

Re: [Puppet-dev] Marking expired puppet resources

d to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-dev@googlegroups.com. > Visit this group at http://groups.

Re: [Puppet-dev] Marking expired puppet resources

op receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-dev@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-dev?hl=en. > For more options, visit https://groups.google.com/groups/opt

Re: [Puppet-dev] Re: Puppet Heredoc (ARM-4) Submitted

On Apr 23, 2013, at 6:17 PM, Henrik Lindberg wrote: > On 2013-24-04 1:28, Luke Kanies wrote: > >> I'm curious at the chosen syntax here -- is @() a common syntax for >> heredocs? I'm more used to things like: >> >> $foo = <> … >> END >&g

Re: [Puppet-dev] Re: Puppet Heredoc (ARM-4) Submitted

On Apr 23, 2013, at 3:56 PM, Henrik Lindberg wrote: > On 2013-23-04 23:54, Luke Kanies wrote: >> On Apr 23, 2013, at 7:13 AM, Henrik Lindberg >> wrote: > >> >> I'm confused by the 'afunc' in the above examples - its pervasiveness in >>

Re: [Puppet-dev] Puppet Heredoc (ARM-4) Submitted

> (shown above) and then run with the setting --parser future Hi Henrik, I'm confused by the 'afunc' in the above examples - its pervasiveness in your examples implies it's required, but it doesn't actually appear to be based on the ARM. What am I missing? -- L

Re: [Puppet-dev] Extending Puppet::Type::File

On Apr 12, 2013, at 8:21 AM, tio teath wrote: > > > On Tuesday, April 9, 2013 6:30:38 PM UTC+3, Luke Kanies wrote: > On Apr 9, 2013, at 6:06 AM, tio teath wrote: > >> >> >> On Monday, April 8, 2013 8:06:23 AM UTC+3, Luke Kanies wrote: >> On Apr

[Puppet-dev] Modified 'capabilities' armature

le have brought up: https://github.com/lak/armatures/blob/ae14a3c6cc6ec969d72a6096c51fad4ef1070cc6/arm-6.capabilities/capabilities.md Thanks, Luke -- Luke Kanies | http://about.me/lak | http://puppetlabs.com/ | +1-615-594-8199 Join us at PuppetConf 2013, August 22-23 in San Francisco - http://b

Re: [Puppet-dev] puppet-internal: loading ruby files and classes the right way

t, um, there be dragons.It's basically a system for loading and managing subclasses of things (which, you might have noticed, is a constant pattern in Puppet for basically all plugins). If you're really just loading a terminus, chances are that the code you want is already availa

Re: [Puppet-dev] puppet-internal: loading ruby files and classes the right way

er way to do that in puppet, similar to how I can do > it in rails? Aka. some_string.constantize Hi Peter, I'm confident there's an easier way; just the way you're using the autoloader there seems unecessarily complicated. Why are you even using autoloading? Why don't you ju

Re: [Puppet-dev] Extending Puppet::Type::File

On Apr 9, 2013, at 6:06 AM, tio teath wrote: > > > On Monday, April 8, 2013 8:06:23 AM UTC+3, Luke Kanies wrote: > On Apr 7, 2013, at 11:59 AM, tio teath wrote: > >> I would like to use Puppet::Type::File as a base type, and add some custom >> properties to it

Re: [Puppet-dev] Extending Puppet::Type::File

y' before I refactored it a long time ago), but I can't seem to find it now. That makes me even less confident that this will work well. Can you elaborate on what you're trying to do, and why? -- Luke Kanies | http://about.me/lak | http://puppetlabs.com/ | +1-615-594-8199

Re: [Puppet-dev] Issues with self.instances and additional Puppet::Type in array...

mcgav-netapp/blob/master/lib/puppet/provider/netapp_user/netapp_user.rb > > Cheers > Gavin > > > On 5 April 2013 11:15, Luke Kanies wrote: > Ah. You should copy the model in the user/group providers: The providers > have a 'create' method that uses useradd, for i

Re: [Puppet-dev] Issues with self.instances and additional Puppet::Type in array...

then trigger a > modify in flush when required? > Or should I treat any call into flush with a :present ensure as a modify? > Though I vaguely remember that causing a double-call on a resource create - > Once from create, and then another from flush... > > Cheers > Gavin

  1   2   3   4   5   6   7   8   9   10   >