Re: [Puppet-dev] Use catalogs from PuppetDB

On Thursday, July 2, 2015 at 2:20:07 PM UTC+2, 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 > > thi

[Puppet-dev] Use catalogs from PuppetDB

Hello, 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. Is there a way to transform PuppetDB catalogs back to standard

Re: [Puppet-dev] Caching catalogs

will give a > speed boost. > That is quite true. Most of the time in our case, new exported resources mean either a change of code, or a newly classified node (which means new hiera data in our case), so that would actually work. > > On Mon, Jun 29, 2015, 17:43 Raphaël Pinson &g

[Puppet-dev] Caching catalogs

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. I'm thinking (at least in our case) it wouldn't be totally crazy to ca

[Puppet-dev] Annoncing the Puppetfile-updater

Hi fellow devs, Today, we are open-sourcing a Rake task lib we have been using internally to keep our Puppetfiles up-to-date. The code can be found on https://github.com/camptocamp/puppetfile-updater, along with a README. I am hoping this will be helpful to more people, and will welcome feeed

Re: [Puppet-dev] Re: Announcing the Puppet Catalog Diff Viewer

group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/556DD0E9.80907%40alumni.tu-berlin.de > . > Fo

[Puppet-dev] Re: Announcing the Puppet Catalog Diff Viewer

2, 2015 at 9:45:49 AM UTC-4, Raphaël Pinson wrote: >> >> I recently noticed that Zack Smith forked and has been maintaining >> R.I.Pienaars' puppet-catalog-diff. This tool can now produce JSON reports, >> which contain lots of interesting information, but are not ve

[Puppet-dev] Announcing the Puppet Catalog Diff Viewer

Hi all, I recently noticed that Zack Smith forked and has been maintaining R.I.Pienaars' puppet-catalog-diff. This tool can now produce JSON reports, which contain lots of interesting information, but are not very readable for normal human beings. I've been wanting to use the tool for Puppe

[Puppet-dev] Re: Generate README.md from inline doc

wrote: > > On 2015-17-03 12:04, Raphaël Pinson wrote: > > Hello! > > > > > > I'd like to generate the README.md of my Puppet modules from modulesync, > > by getting the docs from the classes themselves. > > > > I've considered using p

[Puppet-dev] Generate README.md from inline doc

Hello! I'd like to generate the README.md of my Puppet modules from modulesync, by getting the docs from the classes themselves. I've considered using puppet-strings, but I don't really see how I could retrieve markdown from it. Is there a way I could get markdown from the inline docs in clas

[Puppet-dev] Re: Recursive dependency checks in rspec-puppet

Anyone has an idea how to do that? On Wednesday, March 11, 2015 at 5:40:00 PM UTC+1, Raphaël Pinson wrote: > > Hello, > > > I've been working on supporting recursive dependency checks in > rspec-puppet today. > > I have a PR for that at https://github.com

[Puppet-dev] Recursive dependency checks in rspec-puppet

Hello, I've been working on supporting recursive dependency checks in rspec-puppet today. I have a PR for that at https://github.com/rodjek/rspec-puppet/pull/261 Unfortunately, I have had to scratch my head for quite a few things, and I'd love to some ideas from you, fellow puppet devs! One

Re: [Puppet-dev] rspec and structured facts

Sorry Kylo, I thought the last post was from Henrik and my phone won't let me see the full thread while replying... -- 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] rspec and structured facts

Thanks for that clarification Henrik. Also, having seen such behaviour before, it appears that PE is patched to default to *not* stringifying facts, unlike the corresponding open source version, which is why your test with PE behaved differently than with bundle. -- You received this message b

Re: [Puppet-dev] rspec and structured facts

Hi Felix, By default, Puppet 3 stringifies all facts. And apparently, "--stringify_facts false" does not work with puppet apply… Raphaël On Monday, March 9, 2015 at 4:13:33 PM UTC+1, Felix Frank wrote: > > Hi, > > me I'm now utterly confused by how this (not) works in the wild. > > $ bundl

[Puppet-dev] Re: rspec and structured facts

Hi Johan, It works for me. By that, I mean I get two errors: * One error for the first test, when it meets $::os['family'], since $::os is not defined in the first test case * One error for the second test, since $::os['release'] is not defined in this case Cheers, Raphaël On Monday, Mar

Re: [Puppet-dev] Improvement version support for gem packages

Yes, https://tickets.puppetlabs.com/browse/PUP-4131 On Monday, March 9, 2015 at 1:47:53 PM UTC+1, Trevor Vaughan wrote: > > +1 for this. Is there a bug to go vote for? > > Thanks, > > Trevor > > On Mon, Mar 9, 2015 at 8:44 AM, Raphaël Pinson > wrote: > >> He

[Puppet-dev] Improvement version support for gem packages

Hello, I've recently tried to use the following syntax for a gem resource: package { 'hiera-eyaml-gpg': ensure => '>= 0.5.pre1' provider => 'gem', } It *does* work, but is not idempotent, since it cannot compare ">= 0.5.pre1" with the installed version "0.5.pre1". The following code

Re: [Puppet-dev] Puppet provider - xml parsing - help needed

to Puppet DSL and vice > versa? > That would be nice. > > Best, > Martin > > > On 26 Feb 2015, at 00:45, Raphaël Pinson > wrote: > > > Hi Martin, > > > > > > Have you considered using an Augeas provider here, using the Xml lens? > >

[Puppet-dev] Re: Puppet provider - xml parsing - help needed

Hi Martin, Have you considered using an Augeas provider here, using the Xml lens? Cheers, Raphaël On Wednesday, February 25, 2015 at 6:18:02 PM UTC+1, Martin Alfke wrote: > > Hi, > > I am stuck at a puppet provider where I need to read data from xml. > > Data which needs to get parsed: >

[Puppet-dev] Autorequiring parent directories to the home directory in user resources

Hello, As per Kylo's comment in PR for PUP-4036 , I'd like to discuss the possibility and implications of autorequiring parent directories of the home directory for user resources. As stated in the PR, the idea came from st

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

On Thursday, November 6, 2014 12:39:22 PM UTC+1, 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,

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

Hi, On Thursday, November 6, 2014 3:37:08 AM UTC+1, henrik lindberg wrote: > > I am bringing up this topic because of a recent discussion and PR for > the ticket https://tickets.puppetlabs.com/browse/PUP-1486 > > Thanks for bringing it up. > Here is a recap. > > The Resources resource is

[Puppet-dev] Re: Leaving Puppet Labs

It's been great working with you. Hope you enjoy your new job as much as this one! -- Raphaël Pinson On Wednesday, November 5, 2014 6:28:23 PM UTC+1, Andy Parker wrote: > > This is one of the hardest emails that I've ever had to write, but the > best way, I suppose, is to

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

7;ll test it out as soon as I am able! > > Trevor > > > On Thu, Feb 27, 2014 at 6:15 AM, Raphaël Pinson > > wrote: > >> Hello, >> >> >> I kept working on this. The current branch (and associated PR at >> https://github.com/hercules-team/auge

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

ources and dependencies). Cheers, Raphaël On Monday, February 10, 2014 4:22:58 PM UTC+1, Raphaël Pinson wrote: > > > On Monday, February 10, 2014 4:14:59 PM UTC+1, Trevor Vaughan wrote: >> >> >> >>> I started working on the flush part. I have a dev branch (

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

On Monday, February 10, 2014 4:14:59 PM UTC+1, Trevor Vaughan wrote: > > > >> I started working on the flush part. I have a dev branch (which doesn't >> pass all tests just now) at >> https://github.com/raphink/augeasproviders/tree/dev/aug_one_handler >> >> Feel free to test it and let me know i

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

s basics, writing facts, functions and providers with the Augeas ruby lib, as well as writing new lenses). Cheers, Raphaël > On Sun, Feb 9, 2014 at 6:09 PM, Raphaël Pinson > > wrote: > >> >> Hi Trevor, >> >> 1) there is an issue open at >> https://githu

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

echanism in the core for cases that Augeas might have a hard time addressing (or devs that would rather not use it). Cheers, Raphaël Pinson -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and sto

[Puppet-dev] Improving Augeas' idempotence in Puppet

Hello, As of today, the way the Augeas provider in Puppet manages idempotence can be somehow problematic. The `onlyif` statements can only be evaluated on the client, so all Augeas resources are generally run on the client, and whether to run them cannot be easily determined in the catalog, unles