Hi folks, We fixed the system binary fallback, and added a few more commands, so we wanted to refresh what's available on rubygems. This is still a development snapshot with a couple of rough edges, b

Hi folks, One missing step from David's original email. If you are running pdk via the cloned git repo, you also will need to set an additional environment variable: PDK_USE_SYSTEM_BINARIES=true and e

Hi folks, in the spirit of release early, release often, we've just opened up the repositories for the pdk to the public: https://github.com/puppetlabs/pdk The README there details some of what is pla

Hi everybody, Vox Pupuli is now a registered freenode group. This means that we can handle out cloaks to everybody who wants one. The current group contacts are our PMC members: Hunner dhoppe nibali

Hi, As Security Officer, I am planning to make a few changes in the way we manage our Github Organization. I would like for us to stop clicking around in the web interface, without any visibility of

Hi all, In the last few months I've chatted with various Vox Pupuli folks about improving the Puppet Forge so that it better supports when modules are deprecated or migrated to a new namespace. Our p

Hi Vox Pupuli folks, We hope you’ll join us for #puppethack on 23 May 2017!  We encourage folks who are new to contributing to join us this time and take advantage of our Open Lab sessions and Getti

Hi Dears, How  I sender my code puppet for Voxpupuli? Atenciosamente, Rafael Tomelin skype: rafael.tomelin E-mail: rafael@... Red Hat Certified Engineer - RHCE Red Hat Certificate of Expertise in Conf

Hi all I already more than once pushed a PR which travis found rubocop etc. problems. I just forgot to run the rake task before pushing. :-p It would have saved me time if it would have been detecte

Hi, have you looked into enabling https://blog.travis-ci.com/2017-03-22-introducing-auto-cancellation ? (see also https://github.com/travis-ci/beta-features/issues/8#issuecomment-288489800 for hints o

Hey all, it looks like people still occasionally mail to the 'puppet-community' google group: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!forum/puppet-community I think this i

Merged, just awaiting release. https://github.com/puppetlabs/puppetlabs-stdlib/pull/737 opened to fix these tests, and David's opened https://tickets.puppetlabs.com/browse/MODULES-4528 for tracking

Hello, It looks like there will be a new Puppet 4.10.x release series soon, which I think is going to cause a few issues in tests for modules and in supporting projects, due to reaching minor version

Overall I think this looks pretty good, but I have some questions and comments. For implementations that can't enumerate all existing resources (at least not in any fast way), like for example File, s

If the goal here is safe execution shouldn’t it escape at least shell special characters? My concern is based on some of the providers I work on which take free form strings as arguments and any type

Hi folks, I've written down the design in README format now. This should make for a easier to ingest from a module developer's perspective. Meanwhile I've also had a shot at a hardcoded implementation

Hi everybody, On modules we currently test these ruby versions with travis: - 2.1.9 - 2.2.6 - 2.3.3 - 2.4.0 I only added 2.1.9 to the Puppet4 matrix because Puppet ships 2.1 in their current AIO pac

Hi, I just wanted to inform you that we dropped Puppet3 support on all of our modules. This also includes Support for Ruby1.8, 1.9 and 2.0. We had some intense sessions in mid January and on the last

I have a module I’d like to import to voxpupuli. I’m following the process outlined at https://voxpupuli.org/docs/#migrating-a-module-to-voxpupuli. This module is complementary to the ‘puppetserver’ m

Honestly, I've never thought the type / provider system was too bad.  Certainly it works pretty well for simple things.  Now, I'm more of a Dev who does Ops than an Op who Devs, but from my perspectiv