[Puppet Users] Is there a way to publish a module via the Forge API?

Hello, I didn't find a way to upload a module to the Forge using the Forge API. Is this possible? I find it a bit weird that a tool which advocates "infrastructure as code" doesn't cater for options to script module uploads. Am I missing something? Thanks. -- You received this message

[Puppet Users] Re: Announce: Puppet Agent 1.5.0, Puppet Server 2.4.0

On May 19, 2016, at 5:54 PM, Eric Sorenson > wrote: > > * Puppet 4.5.0 - Also primarily a bugfix release, with improvements in the > type system and a few hotly awaited fixes for systemd and the DNF package > manager. The release

[Puppet Users] Announce: Puppet Agent 1.5.0, Puppet Server 2.4.0

I'm excited to announce a new batch of backwards-compatible feature releases for the Puppet Agent and Server. There's a lot to take in here, so check out the release notes and take the code for a test-drive before you yell out "YOLO!" and upgrade all of production. Puppet Server 2.4.0 - A

Re: [Puppet Users] the issues with thias/fooacl: filesystem ACL

On Thu, May 19, 2016 at 5:04 PM, Sans wrote: Hi there, > > Is anyone using thias/fooacl > module? I use it for > WordPress, to give www-data read access to wp-config.php and few other > files. Every time puppet runs, the

[Puppet Users] the issues with thias/fooacl: filesystem ACL

Hi there, Is anyone using thias/fooacl module? I use it for WordPress, to give www-data read access to wp-config.php and few other files. Every time puppet runs, the file becomes unreadable: # file: wp-config.php # owner: root # group: root

Re: [Puppet Users] Error with EPP template from "Learning Puppet 4"

On Thu, May 19, 2016 at 2:52 PM, David Karr wrote: > On Thursday, May 19, 2016 at 2:36:53 PM UTC-7, Peter Huene wrote: > >> >> On Thu, May 19, 2016 at 2:23 PM, David Karr >> wrote: >> >>> On Thursday, May 19, 2016 at 2:16:17 PM UTC-7, Peter

Re: [Puppet Users] Error with EPP template from "Learning Puppet 4"

On Thursday, May 19, 2016 at 2:36:53 PM UTC-7, Peter Huene wrote: > > > On Thu, May 19, 2016 at 2:23 PM, David Karr > wrote: > >> On Thursday, May 19, 2016 at 2:16:17 PM UTC-7, Peter Huene wrote: >>> >>> Hi David: >>> >>> On Thu, May 19, 2016 at 1:57 PM, David Karr

Re: [Puppet Users] Error with EPP template from "Learning Puppet 4"

On Thu, May 19, 2016 at 2:23 PM, David Karr wrote: > On Thursday, May 19, 2016 at 2:16:17 PM UTC-7, Peter Huene wrote: >> >> Hi David: >> >> On Thu, May 19, 2016 at 1:57 PM, David Karr >> wrote: >> >>> I'm stepping through "Learning Puppet 4",

Re: [Puppet Users] Error with EPP template from "Learning Puppet 4"

On Thursday, May 19, 2016 at 2:16:17 PM UTC-7, Peter Huene wrote: > > Hi David: > > On Thu, May 19, 2016 at 1:57 PM, David Karr > wrote: > >> I'm stepping through "Learning Puppet 4", and I ran into an error >> following steps in the book, and I want to understand what

Re: [Puppet Users] Error with EPP template from "Learning Puppet 4"

Hi David: On Thu, May 19, 2016 at 1:57 PM, David Karr wrote: > I'm stepping through "Learning Puppet 4", and I ran into an error > following steps in the book, and I want to understand what went wrong > before I report it. > > The section in question is "Using Puppet

[Puppet Users] Error with EPP template from "Learning Puppet 4"

I'm stepping through "Learning Puppet 4", and I ran into an error following steps in the book, and I want to understand what went wrong before I report it. The section in question is "Using Puppet EPP Templates" in chapter 13. I'll work backwards from the error I'm getting, showing the

[Puppet Users] Announce: PuppetDB 4.1.0 is now available

PuppetDB 4.1.0 - May 19, 2016 === PuppetDB 4.1.0 is a backward-compatible feature release that adds packages for Ubuntu Xenial - 16.04, Ubuntu Wily - 15.10, adds preliminary support for HUP signal handling, and improves the speed of removing old reports, and of

Re: [Puppet Users] Logrotate module broken, string 'undef' now treated as undef

Here's some code to try: $var1 = undef $var2 = "undef" $var3 = 'undef' $var4 = "'undef'" $var5 = '"undef"' notify { "VAR1: ${var1} VAR2: ${var2} VAR3: ${var3} VAR4: ${var4} VAR5: ${var5}": } When run, this results in: Notice: VAR1: VAR2: VAR3: VAR4: 'undef' VAR5: "undef" On

Re: [Puppet Users] How to control who can add/update permissions in sudoers

This is probably something that should be addressed via code management or audits, rather than via puppet. It can't really know e intentions, so if someone wants to exec 'rm -fR' it will gleefully let it happen. It's on you to trust your developers and have a pipeline to test things. Canary nodes

Re: [Puppet Users] puppet 4 environments git feedback?

We use a cron job in addition to git hooks. The hooks work 99% of the time, and the cron job handles the occasional miss because the network burped. They're very complimentary. On Thursday, May 19, 2016, Christopher Wood wrote: > On Thu, May 19, 2016 at 11:39:30AM

Re: [Puppet Users] puppet 4 environments git feedback?

On Thu, May 19, 2016 at 11:39:30AM -0400, Rob Nelson wrote: >Doug, > >If all your git repositories are local filestores, that's probably a >pretty reasonable workflow. However, most people use some form of >dedicated service as their git origins, that reside external to the local

Re: [Puppet Users] Re: How to control who can add/update permissions in sudoers

Problem is that if you don't have a way of limiting where sudo entries can be made, someone can create a new module and grant themselves full sudo rights there for a large number of systems. When in a large enterprise such as ours, there are modules that are created and maintained by teams

Re: [Puppet Users] puppet 4 environments git feedback?

Doug, If all your git repositories are local filestores, that's probably a pretty reasonable workflow. However, most people use some form of dedicated service as their git origins, that reside external to the local systems - GitHub, Bit Bucket, Git Lab, etc. If you are using one of those systems,

Re: [Puppet Users] Re: How to control who can add/update permissions in sudoers

I was coming in here to say the same thing John said. Your sudoers definition is going to be a combination of code (include sudo; sudo::conf {'whatever':}) and data (the sudo::conf attributes). That data can be embedded in your code, or come from a hiera/lookup backend. Both of those should be in

Re: [Puppet Users] Logrotate module broken, string 'undef' now treated as undef

puppetserver: 2.3.2-1puppetlabs1 puppet client: 3.8.5-2~bpo8+1 Both server and clients are running Debian 8 (jessie); the puppet client is from the Debian backports repo. On Wed, May 18, 2016 at 3:40 PM, Matthaus Owens wrote: > Daniel, > Which version of Puppet are you

[Puppet Users] Re: How to control who can add/update permissions in sudoers

On Wednesday, May 18, 2016 at 7:05:48 PM UTC-5, Alex Scoble wrote: > > Hi all, > > We're currently on PE 3.8.4. > > We need to be able to manage sudoers permissions with Puppet, but control > things so sudoers permissions can only be granted within a specific module. > > So permissions could be

[Puppet Users] How to control who can add/update permissions in sudoers

Look for assert_private in puppetlabs-stdlib module. Maybe its what you are looking for. Thomas -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [Puppet Users] Message from application: cannot load such file — puppet/util/command_line (LoadError)

First off. As of Puppet 4 is the server part written in Clojure and runs on the JVM, the parts that are still Ruby are also ran on the JVM with JRuby. Secondly is the package an all in one package, so no third party or system ruby should be running. You should not need Apache or Passenger, just