[Puppet-dev] Re: Puppet Strings Module Release

So happy to see continued development on this! On Wednesday, 23 September 2015 22:33:49 UTC+2, Ian Kronquist wrote: > > We’re excited to announce the latest release of the Strings module! > Strings generates HTML documentation from inline comments and is designed > to replace *puppet doc*. Strin

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

15 people so far, not bad. I like Meg's suggestion as they should be able to fit us all without problems so for now lets settle on the following: Date: 2015-10-06, aka the 6th of October 2015 Time: 15:30 PDT (UTC-7) Location: Tea Zone & Camellia Lounge at 510 NW 11th Avenue I created an event o

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

Hi everyone, As is tradition (since last year) I'm organising a pre-contributor-summit tea party at some decent tea place in Portland. We shall assemble at the to be announce tea shop at 15:30 local time. If you live in Portland and know of a good tea place (not a Starbucks or random coffee sh

Re: [Puppet-dev] Feature proposal: external environment locator (EEL)

Hi, It would really help if you elaborated on your use cases in this thread. I read the one message you linked but I'm still not sure about it and I don't feel like reading the whole other thread to get context. If you propose a feature part of that proposal should be a rationale and intended u

Re: [Puppet-dev] Re: Module PR Triage Notes 2015-02-26

Ah! You have an invite now :). On Wednesday, 4 March 2015 20:12:42 UTC+1, Hunter Haugen wrote: > > No merge access? > > > > -Hunter > > On Tue, Mar 3, 2015 at 9:27 AM, Daniele Sluijters > wrote: > >> Ahem, why u no >> https://github.com/puppet-comm

[Puppet-dev] Re: Module PR Triage Notes 2015-02-26

Ahem, why u no https://github.com/puppet-community/community-triage/tree/master/modules/notes? On Thursday, 26 February 2015 20:12:56 UTC+1, Hunter Haugen wrote: > > Here are the notes from this weeks module PR triage which happens every > week at 10:00am PST or PDT in #puppet-dev on Freenode >

Re: [Puppet-dev] Beaker-extensions

Hi, I would be interested to help out here too. We need things like a custom provider for our own cloudy thing at Spotify and a few other extension points so that we can move away from rspec-system-puppet . On Sunday, 30 November 2014 23:54:40 UTC+1, Justin Stoller wrote: > > I've been working

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

> > First question is, can you gracefully deprecate a line of agents, i.e. > retain 3.x agent compatibility throughout 4.x masters, and drop it at 5.0. > I shall assume that the engineering effort to go such a route would be a > magnitude or two above just dropping cross-version support, so doi

[Puppet-dev] Re: Leaving Puppet Labs

No. I do not accept. :( Thank you, for so much, for your code, your contributions and your patience. It's been a privilege. Best of luck and don't be a stranger! -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this g

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

Agreed. This is a tool that 'ops' people should also be able to use and not require a black belt in C type casting or an understanding of the parser to figure out when a string is actually a string and will be treated as such. On Monday, 3 November 2014 22:06:03 UTC+1, Thomas Hallgren wrote: > >

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

> > I was also bitten by this during testing and it made the thought of > converting my code to 4.0 daunting. The auto conversion also holds for the current parser, so I don't see how that's making anything different, or daunting. Essentially what it comes down to is input sanitisation. Up un

[Puppet-dev] Re: Puppet Master Profiles

So I ran the script: Do you wish to continue and have the script generate a /var/log/puppet/profile.yml file? [Y/n]: Y Script canceled by user. It works with 'y', just not 'Y', which is a bit stupid. I realise that Y just means "I default to y" but the capitalisation shouldn't matter :). -- Y

[Puppet-dev] Re: Merits of directory environments and opt-in fallback mode?

> (where all environments were promoted to 'production' if they weren't configured in puppet's configuration) What do you mean here, exactly? > however the current design I'm thinking could benefit from it. Can you give a rationale / use case that would benefit from this? As you present it now

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

The fix Andy pushed out (PUP-3201) is working for me now, I can get all cases to pass that I couldn't before. I'm sure there's a few tests that need adjusting and a few more that should be put in place but the fix itself seems to be working without having broken anything else for me. -- You re

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

Friday, 10 October 2014 00:06:31 UTC-7, Daniele Sluijters wrote: > > Hi list, > > As an exercise to get me familiar with the new type system I started a > from-scratch rewrite of the apt module (don't worry I won't publish it like > that). The reasons for this are leg

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

e 'undef' to specify a form of 'nothingness' so that the default for that parameter on the type we were passing it is was respected are now handled by undef. -- Daniele Sluijters On Friday, 10 October 2014 07:28:09 UTC-7, henrik lindberg wrote: > > Thanks Daniele, ex

[Puppet-dev] Experiences with the new type system

;m utterly confused. It looks like I can't have Optional accept undef on a 'top' parameter, I can use it on a hash and initialise that hash with a key that is set to undef but I cannot pass in a hash with that same key set to undef. Maybe I've misunderstood the behaviour of Opti

[Puppet-dev] Re: Removing types/providers from core

I completely missed 'tidy', that was a copy-paste gone wrong. I really have no preference towards that one but John makes a good argument that the way it interacts with file would warrant it to stay in core. Mount on the other hand can only work with mount/umount and is chained to /etc/fstab or

[Puppet-dev] Removing types/providers from core

riteria? Does PL want to carry them in their own namespace or should we move most of this to puppet-community? P.S The puppet-community space on Github is open to everyone who wants to contribute to it, include PL employees. It's just not tied to Puppet Labs, governance wise, which gives us

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

Separate types undoes basically what "package" now tries to make as transparent as possible. I guess a case could be made to have "package" only deal with the OS native package provider and have separate types and providers for "secondary" packages like gem, wheel/egg/whatever etc. On Tuesday,

[Puppet-dev] Re: Announce: Puppet Strings 0.1.0 Released

First, congratulations this is awesome and will make a lot of people very happy! Second, typo in the README: puppet strings serever, that's one 'e' too many. Third, is there an example module annotated with yard-style documentation to give a people an idea of how to get this going? Some example

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

Well, we're not going to stick around for tea until dinner but there's plenty we can do in the mean time! -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to p

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

Attached an ICS for tea time. I hope it survives the time zones. -- You received this message because you are subscribed 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

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

t; > sound good). I have dinner plans, so I'll play post-dinner drinks by > ear. > > > > On Thu, Sep 18, 2014 at 11:23 PM, Daniele Sluijters > > > wrote: > >> > >> I'm staying up on Lombard St. near the Golden Gate Park so I'm just

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

I'm staying up on Lombard St. near the Golden Gate Park so I'm just going to Uber around to wherever everyone else is. There's Leland Tea Company on 1416 Bush St. or Samovar at 730 Howard St. / Yerba Buena Gardens. -- You received this message because you are subscribed to the Google Groups "

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

st hanging out around the Golden Gate park (just an example) * dinner * drinks afterwards Don't worry, you don't have to do all three, just trying to gauge if there's any interest into getting together sometime on Sunday. -- Daniele Sluijters -- You received this message b

[Puppet-dev] Re: Lightweight PuppetDB replacement

your point about PuppetDB and the JVM. I'd also like to see some real examples of your gripes with the PuppetDB API. I'd also like to hear how PuppetDB complicates your testing? In both cases you need a database, PuppetDB even makes this easier because it can run in-memory. -- Dani

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

> 2) warn people about cases where where using code in other languages could lead to problems. Unless we want to keep track of every language and how the multiple libraries that exist handle serialisation and deserialisation that's pretty much impossible. "Oh but this breaks in Scala but works

Re: [Puppet-dev] Facter version guarantees

Lets take is_virtual as an example. That fact, and all the boolean facts, have been strings since the dawn of time. During the first days of creation people wrote manifests that went if $is_virtual == 'false' {}. By now, most if not all, DSL consumers are aware of the 'correct' way to do this,

[Puppet-dev] Re: [Puppet Users] Re: Announce: Facter 2.2.0

have come to expect at least some 'breakage' on .Y releases, regardless of wat semver says (that's not anything personal towards Puppet Labs, it happens on a lot of projects). -- Daniele Sluijters -- You received this message because you are subscribed to the Google Groups "

[Puppet-dev] Re: Announce: Facter 2.2.0

ate you're stuck with manually patching an upstream module and carrying that change. Depending on how you deploy your environment this might be difficult to do. -- Daniele Sluijters -- You received this message because you are subscribed to the Google Groups "Puppet Developers&qu

[Puppet-dev] Re: This is a trivial contribution.

d but having the CLA bot involved needlessly complicates the contribution process to modules. I can understand this happening on the core products because they're dual-licensed, the modules however are not and we should not put up more obstacles for contributors, we should be removing them. -

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

What Nick, Henrik and Erik said. Rename the old tool, deprecate it and remove it. `puppet doc` is the command that makes sense and that sensible command should do sensible things. I kinda do like 'codex' though, it has a ring to it. -- Daniele Sluijters On Tuesday, 12 August 201

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

Please don't use `dox`. It's like a teenager who wasn't taught enough English in school, or simply doesn't care, to know that the accepted plural of doc is docs, not dox, dawg. On Tuesday, 12 August 2014 19:33:04 UTC+2, Andy Parker wrote: > > On Tue, Aug 12, 2014 at 10:19 AM, Hailee Kenney > wr

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

Because 3 is always better than 2 SaaS services, has any consideration been given to Codeclimate? We've been using it at Nedap for a while now and so far it has helped identify some (big) issues in our code bases and helped us keep new projects on track. Their 'security monitor' is remarkably u

[Puppet-dev] Collectors, resource defaults and the realisation side-effect

resources or 'bags' of resource types in the catalog and have that relation taken into account when the resource is realised, without causing realisation at that point. -- Daniele Sluijters -- You received this message because you are subscribed to the Google Groups "Puppe

[Puppet-dev] Re: First anniversary of the module team

Sounds great! <3 and happy birthday (albeit a few days late but feel free to consume more cake). On Wednesday, 25 June 2014 18:53:25 UTC+2, Ashley Penney wrote: > > The 1st anniversary of the module team! > > Hello from the module team here at Puppet Labs! I’m starting this email > with a lie b

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

> So, if you're willing to depend on other modules, then I think ripienaar/module-data combined with explicit lookups can do a lot of what you're after. Honestly, that should just be part of Puppet core. It's such an incredibly useful featur

[Puppet-dev] Re: is there any way to audit the contents of a file using puppet

This is a question for puppet-users, don't just cross-post in order to get more visibility please. On Friday, 30 May 2014 18:57:05 UTC+2, Supriya Uppalapati wrote: > > Hi, > > is there any way to audit the content of a file using no-op in puppet. > > Help me. > -- You received this message

[Puppet-dev] Re: Environment Caching - RFC

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 one to do it with a SIGHUP or USR1/2). The only way I can see this working for most people is

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

I'm with Trevor here. A Face to interact with environments and query for state would be really helpful to debug such issues or force a refresh. On Monday, 28 April 2014 20:55:02 UTC+2, Trevor Vaughan wrote: > > "OTOH, for a new user who is just starting to try things out, having it > watch a sin

[Puppet-dev] True/false and nil

where Puppet is checking for truthiness instead of nullity. If you have a use case where you're working around behaviour involving Booleans that you think should work in a sane way, please please please raise a ticket and link it there. Puppet 4 is our chance to get this insanity sorted. -

Re: [Puppet-dev] Re: Changes to PuppetDB to support proper environments

I always found it surprising and slightly confusing that exec has an 'environment' attribute, I expected that to be a metaparam that could be applied to any resource to indicate what environment it should belong to (defaulting to the current one). Would get freaky as you could then export resou

Re: [Puppet-dev] Re: Best practices for ensure property values

rate parameters for readability (which > > translates to being easier to parse with external scripts if necessary). > > > > Trevor > > > > > > On Tue, Apr 1, 2014 at 9:09 AM, Daniele Sluijters > > > > <mailto:daniele@gmail.com>> >

[Puppet-dev] Re: Best practices for ensure property values

If we go down this road, how does 'purged' fit in. Should we have purge => true, or ensure => 'purged'? On Wednesday, 26 March 2014 19:12:33 UTC+1, Jesse Hathaway wrote: > > In my discussion with @adrienthebo on my pull request: > https://github.com/puppetlabs/puppet/pull/2309 I raised the quest

Re: [Puppet-dev] Re: Changes to PuppetDB to support proper environments

better for community modules. What if your module ships with it's own native type and you want to collect on those? If you need to explicitly pass an environment for collection to even work, what do you pass, 'production' and hope that everyone works from that environment? -- Dani

Re: [Puppet-dev] Re: Changes to PuppetDB to support proper environments

tored by my Nagios instance which happens to be running on the production environment. -- Daniele Sluijters -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an e

Re: [Puppet-dev] Re: Changes to PuppetDB to support proper environments

The one issue I see with that approach is what happens when your monitoring system, *choke* nagios *choke* is dependant on said exported resources. Wiping the database clean isn't really an option in that case or you'd need to temporarily disable reloading your monitoring until everyone's checke

[Puppet-dev] Re: Best practices for ensure property values

o other package managers though. As far as 'ensure => directory' on a file goes I don't really mind that syntax, in my mind a directory is just a special file, much like a symlink is or a socket. A separate directory type might be interesting if it has extra magical powers that

[Puppet-dev] Module Team: Spring cleaning

we'll have more time during the next session to actually discuss the PR's that warrant discussion and once we run out of those have room for other topics. I'll keep combing through apt and add mysql and firewall to my plate. Anyone else that can take on a few modules so we can do

[Puppet-dev] Re: We're changing the module community triage/meeting date and time!

Yay timezones. A little lesson on timezones. Portland is in either PST or PDT. S doesn't stand for summer is stands for Standard, aka when daylight savings is not in effect. The D in PDT stands for Daylight, aka when daylight savings is in effect, ergo wat most Europeans would consider Summer w

[Puppet-dev] Re: The 4x scope

Hi, I like just about everything in the proposal but I have my doubts about this: > The class scope looks up unqualified variables in the class itself, if > not found there, it continues up the parent chain of scopes. If the > class inherits from another, then, the parent scope is one that >

[Puppet-dev] Re: hiera-puppet-helper: unexpected behaviour when testing conditions

e-setting hiera_data doesn't work. I have no experience whatsoever with hiera-puppet-helper though so I might be getting this all wrong. -- Daniele Sluijters On Monday, 24 February 2014 17:48:44 UTC+1, Brian Warsing wrote: > > Hi, > > I hope this on-topic. Let me know if I s

[Puppet-dev] Re: ROADMAP/REDESIGN: Puppetlabs-mysql

Hi, That user that asked his DBA was me so you know most of our issues with the module by now. One that's especially high on my list is the SSL client certificate stuff, both for c2s and s2s connections but also for user authentication. I'm also liking the idea of splitting this module up, it w

Re: [Puppet-dev] Directory Environments

Hey, As far as I can see I see no reason why your setup wouldn't work, at least not once it's feature complete in 3.6.0. All in all, this sounds great to me! -- Daniele Sluijters On Friday, 21 February 2014 14:13:59 UTC+1, Jason Antman wrote: > > My heart stopped when I r

Re: [Puppet-dev] Re: Solving `if defined(Resource['name'])`

I like a constrains style solution much better myself to, wasn't aware of it at the time. I think with Puppet 4 we could introduce some additional pain, semver wise we'd be allowed to do that. If that helped fix this issue once and for all I'm pretty sure the community would support it too. On

Re: [Puppet-dev] Solving `if defined(Resource['name'])`

ral, I've found that if you make these optional, you stand a >> pretty good chance of staying out of people's way and letting them manage >> those portions their way while still taking advantage of your module. >> >> All that said, I still want to be able to decl

[Puppet-dev] Solving `if defined(Resource['name'])`

desirable or possible to solve this issue in the first place but I was curious if anyone has given any more thought to this? -- Daniele Sluijters -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and sto

[Puppet-dev] Re: on the future of stdlib...

I was browsing through stdlib and I noticed that there's quite a few things in there that make me itch, from a little to a lot very much. Most of them are workarounds for features missing in the Puppet language and though I understand why they exist a few are a bit iffy. To take an example, fil

Re: [Puppet-dev] Re: Module PR Triage tomorrow: puppetlabs-apache

Hi, That's okay, this was bound to happen sooner rather than later. I can actually make it though I doubt I'll have much useful input as I've barely touched puppetlabs-apache. I'll join in if there are seats left a few minutes in. -- Daniele Sluijters On Tuesday, 11 Fe

[Puppet-dev] Re: Module PR Triage tomorrow: puppetlabs-apache

Hi, Would you mind specifying what tomorrow is? Depending on the timezone you're living in versus the timezone I'm reading this in my tomorrow might not be your tomorrow. I'm guessing tomorrow is the 12th of february? -- Daniele Sluijters On Tuesday, 11 February 2014 04:06

[Puppet-dev] Cfgmgmt: ParsedFile vs Augeas discussion

ling lists and if you agree with the general sentiment of the ticket feel free to vote for it. -- Daniele Sluijters -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from i

Re: [Puppet-dev] Announce: PuppetDB 1.5.0 Available

It's not just the Precise packages that are missing. The complete Debian suite is missing too, squeeze, wheezy, jessy and sid. On Tuesday, 1 October 2013 04:59:16 UTC+2, blkperl wrote: > > No packages for precise/raring? Its missing debs for 1.5.0. Lucid seems > fine > > Thanks, > William > > >

[Puppet-dev] Re: Announce: PuppetDB 1.5.0 Available

Oh goody this looks awesome. -- Daniele Sluijters On Tuesday, 1 October 2013 01:56:49 UTC+2, Chris Price wrote: > > PuppetDB 1.5.0 is now available for download! This is a new feature > release that contains a few bug-fixes as well. > > =

Re: [Puppet-dev] The security of the puppet master.

master but also for other applications (like web applications) that are deployed to different servers. -- Daniele Sluijters -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving ema

[Puppet-dev] Re: Announce: PuppetDB 1.4.0 Available

Hey, Great work! I really like the addition of puppetdb-anonymize, that's going to help me out in a few situations. -- Daniele Sluijters On Friday, 9 August 2013 01:59:25 UTC+2, Ken Barber wrote: > > PuppetDB 1.4.0 is now available for download! This is a new feature > release