Jira (PUP-9507) Plusignment on defined types ignores default value

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9507  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plusignment on defined types ignores default value   
 

  
 
 
 
 

 
 I don't have any opinion on the correctness of the change, but that's because I don't understand what problem led to the creation of the code that exhibits the bug. Virtual resources + plussignment are two features of the language I've personally never needed to use. I agree that we wouldn't want to change the existing behavior because it'd almost certainly have unintended consequences for other users.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9487) Prepare release announcement (Puppet Platform 6.3.0)

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9487  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prepare release announcement (Puppet Platform 6.3.0)   
 

  
 
 
 
 

 
 
 
Subject: Puppet Platform 6.3.0 is now available! 
The next monthly release in the Puppet 6 series is now available. Puppet Platform 6.2.0 includes security improvements, bug fixes, and backwards-compatible feature updates to Puppet Server, Puppet Agent, and Facter. Highlights of this release include: 
 
Updates to Puppet Server's SSL (bouncycastle) library from upstream to address security issues (SERVER-2431) 
Support for macOS Mojava (10.14) agents (PA-2226) 
An improvement to the Puppet agent's log output to distinguish between intentional change (additional or updated resources in the catalog) and corrective change (drift detected on the node) (PUP-9324) 
 
View the full release notes and installation information: https://puppet.com/docs/puppet/6.3/puppet_index.html 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet 

Jira (PUP-9357) Noop exec debug logging should include the command

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9357  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Noop exec debug logging should include the command   
 

  
 
 
 
 

 
 Hm, so the code snippet would be  
 
 
 
 
 exec { 'example':   
 
 
   command => Sensitive.new('/bin/true'),   
 
 
   unless => Sensitive.new('/bin/false'),   
 
 
 }
  
 
 
 
  Like Chris Roddy I don't have any evidence that people need this today but if it's easy to add, then sure, go for it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

  

Jira (PUP-9324) Puppet agent run output to differentiate between corrective and intentional change

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9324  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet agent run output to differentiate between corrective and intentional change   
 

  
 
 
 
 

 
 Halim Wijaya it will be in the next LTS patch release, PE2018.1.8.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9442) Prepare release announcement (Puppet Platform 6.2.0)

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9442  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prepare release announcement (Puppet Platform 6.2.0)   
 

  
 
 
 
 

 
 
 
Subject: Puppet Platform 6.2.0 is now available! 
The next monthly release in the Puppet 6 series is now available. Puppet Platform 6.2.0 includes bug fixes and backwards-compatible feature updates to Puppet Server, Puppet Agent, and PuppetDB. In addition to rolling up the bug fixes from last week's 6.0.5 patch release, it includes: 
 
A new logging format for Puppet output that's human-friendly line oriented JSON output (PUP-8687) 
Package provider improvements for both Solaris (PUP-5287) and Portage (PUP-9071) providers 
A fix for running Puppet Server under JDK 11 (SERVER-2404) 
 
Special thanks to Daniel Klockenkämper for the Portage improvements and Romain Tartière for the JSONL contribution! 
View the full release notes and installation information: https://puppet.com/docs/puppet/6.2/puppet_index.html 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   

Jira (PUP-9151) Schedule resource weekly behavior inconsistent with other periods

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9151  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Schedule resource weekly behavior inconsistent with other periods   
 

  
 
 
 
 

 
 I think we'd take a patch that addresses this, it's not widely used but I understand the logic. Jo Rhett - you've probably used 'schedule' more than any human on this blue globe - have you run into this before? What do you think about the proposed solution?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9452) Puppet Device application should support --disable flag like the Puppet Agent does.

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9452  
 
 
  Puppet Device application should support --disable flag like the Puppet Agent does.   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Team: 
 Network Automation  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9452) Puppet Device application should support --disable flag like the Puppet Agent does.

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9452  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet Device application should support --disable flag like the Puppet Agent does.   
 

  
 
 
 
 

 
 Ping Thomas Honey and David Schmitt - not sure how to best track device tickets.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9452) Puppet Device application should support --disable flag like the Puppet Agent does.

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9452  
 
 
  Puppet Device application should support --disable flag like the Puppet Agent does.   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Key: 
 SERVER PUP - 2438 9452  
 
 
Project: 
 Puppet  Server  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6571) An invalid path to the --logdest option is silently ignored

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-6571  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: An invalid path to the --logdest option is silently ignored   
 

  
 
 
 
 

 
 yeah that makes sense to me.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9376) Prepare release announcement (Puppet Platform 5.5.10)

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9376  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prepare release announcement (Puppet Platform 5.5.10)   
 

  
 
 
 
 

 
 Since 5.5.10 and 6.0.5 are very similar payloads for different release streams, I'm going to combine the mails to prevent "announcement fatigue". Draft below: 
 
Subject: Puppet Platform 5.5.10 and 6.0.5 are now available 
Happy New Year! The first set of releases for the Puppet 5.5 (LTS series) and Puppet 6.0 (Feature series) are available. These releases contain bug fixes and performance improvements, notably: 
 
Added support for Fedora 29 and removed Fedora 27. 
Fixed a long-standing performance problem in the Puppet Module Tool, resulting in much faster module installations 
Performance and correctness improvements for highly-available PuppetDB that should improve startup time 
 
As always you can see the full list of changes in the release notes: For Puppet 5.5.10: https://puppet.com/docs/puppet/5.5/release_notes.html For Puppet 6.0.5: https://puppet.com/docs/puppet/6.0/release_notes_osp.html 
Special community thanks for these releases go to Jared Ledvina for the SELinux fixes in PUP-9330 and to Matthias Baur for the detailed troubleshooting info that led to fixing the Puppet Module slowdown in PUP-9364. 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
  

Jira (PUP-9396) Last run summary doesn't indicate that the run failed

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson assigned an issue to Eric Sorenson  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9396  
 
 
  Last run summary doesn't indicate that the run failed   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Assignee: 
 Eric Sorenson  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (BOLT-988) Task for making http/https requests with bolt.

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-988  
 
 
  Task for making http/https requests with bolt.   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 

  
 
 
 
 

 
 bolt should ship with a task that makes it easy to make web requests.params:url  - fully qualified url scheme method  - get, put, post, delete (default to get) body  - optional headers  - hash of header name:value cacert  - for trusting the remote end, maybe create a ssl obj? cert  - present for client auth key  - private key for the client cert parse_response  - whether or not to treat the response as json This should be a task so that it can get information from inside the datacenter.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this 

Jira (BOLT-988) Task for making http/https requests with bolt.

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson assigned an issue to Eric Sorenson  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-988  
 
 
  Task for making http/https requests with bolt.   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Assignee: 
 Eric Sorenson  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9339) Refreshed resources do not get a status event in the report

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9339  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Refreshed resources do not get a status event in the report   
 

  
 
 
 
 

 
 Kris Bosland can you please add a Release Note for this issue? it's pretty esoteric but has the possibility of changing what people see in reports so it's probably worth surfacing in the docs. (Apologies if this is already in one of the linked tickets)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9350) Prepare release announcement (Puppet Platform 6.1.0)

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9350  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prepare release announcement (Puppet Platform 6.1.0)   
 

  
 
 
 
 

 
 ping Jean Bond - can i get a review of the announcement? feel free to edit my comment inline with any changes ^^  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9350) Prepare release announcement (Puppet Platform 6.1.0)

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9350  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prepare release announcement (Puppet Platform 6.1.0)   
 

  
 
 
 
 

 
 
 
Subject: Puppet Platform 6.1.0 is now available! 
The first feature release in the Puppet 6 series is now available for download. This is a backwards-compatible release which contains a mixture of bugfixes and enhancements. It includes component updates to Puppet Server, Agent, and PuppetDB. 
Of particular note for this release: 
 
Puppet Server has a JRuby update that implements Ruby 2.5 and has experimental support for Java 11. 
PuppetDB now uses "ahead-of-time" (AOT) compilation for a performance boost when starting up and issuing commands. 
The Puppet Agent contains a number of type and provider fixes, including a configurable timeout for service operations on Windows, support for systemd on Linux Mint 18 and 19, and selinux improvements. Additionally, a long-standing bug which prevented some kinds of notified resources (like reboots and execs) from showing up in reports is now fixed (PUP-9350) 
 
A special community shout-out for this release goes to Jared Ledvina, for the selinux improvements in PUP-9330! 
As always, see the release notes for the full list of changes in this release: https://puppet.com/docs/puppet/6.1/release_notes_osp.html 
--eric0
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
   

Jira (PUP-9365) Newlines in resource titles result in invalid .dot files

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson assigned an issue to Mihkel Ader  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9365  
 
 
  Newlines in resource titles result in invalid .dot files   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Assignee: 
 Mihkel Ader  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9365) Newlines in resource titles result in invalid .dot files

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9365  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Newlines in resource titles result in invalid .dot files   
 

  
 
 
 
 

 
 Titles with newlines are kind of unspecified behaviour - what is the problem you are trying to solve here? cc Henrik Lindberg - not sure if a title with embedded newline is even an acceptable syntax  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9324) Puppet agent run output to differentiate between corrective and intentional change

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9324  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet agent run output to differentiate between corrective and intentional change   
 

  
 
 
 
 

 
 I rather like jarrett's second suggestion - just to flag the corrective changes rather than all changes. This seems like a low effort / low risk way to solve the problem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9254) Agent Functions - add eval() function

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9254  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Agent Functions - add eval() function   
 

  
 
 
 
 

 
 no, I wasn't aware of this work. On the merits it seems like kind of a bad idea. If you had formatting, munging, etc, to do from a Deferred value, why wouldn't you just do that in the function itself? To me, that boundary is very clean and simple. Adding more complexity to the agent-side language evaluation muddies the waters quite a lot. Henrik Lindberg has any user asked for this? Without some really concrete use cases and problems that cannot be solved any other way, I would be opposed to continuing down this path.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8002  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Attempt to redefine entity" caused by using a resource collector
 

  
 
 
 
 

 
 Henrik Lindberg could you please pull this back to the 5.5.x series as well? it should have been slated for that in the first place since that's the customer request.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9267) The members property's 'retrieve' and 'should' methods should return arrays

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9267  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The members property's 'retrieve' and 'should' methods should return arrays   
 

  
 
 
 
 

 
 yes, this change was ticketed as a no-behaviour-change refactor. Eric Sorenson - e...@puppet.com   director of product  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9247) Puppet pidlock checks only look for PID if it is running, not process name

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9247  
 
 
  Puppet pidlock checks only look for PID if it is running, not process name   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Team: 
 Platform  Core  OS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8899) New setting to allow external control over start of puppet run

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8899  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: New setting to allow external control over start of puppet run   
 

  
 
 
 
 

 
 Matthias Hörmann this seems like you want to overload a lot of "external" behaviour into puppet. If you already have an outside script to decide whether puppet should run, could that not also inject randomness into the restarts? This is a common pattern even for normal agent usage, if people want more sophistication than the built-in splay.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8899) New setting to allow external control over start of puppet run

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson assigned an issue to Matthias Hörmann  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8899  
 
 
  New setting to allow external control over start of puppet run   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Assignee: 
 Eric Sorenson Matthias Hörmann  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8899) New setting to allow external control over start of puppet run

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson assigned an issue to Eric Sorenson  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8899  
 
 
  New setting to allow external control over start of puppet run   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Assignee: 
 Eric Sorenson  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8002  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Attempt to redefine entity" caused by using a resource collector
 

  
 
 
 
 

 
 I put up https://github.com/puppetlabs/puppet/pull/7162 which might address this? Would love to see if someone with the problem can try it out  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8002  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Attempt to redefine entity" caused by using a resource collector
 

  
 
 
 
 

 
 Spent some time with Sean Millichamp digging through this - some more details 
 
The error happens sporadically and only compiling on sles, which has a collector for inifile resources  
 
 
 
 
 Ini_setting <| title == 'zypper pc_repo autorefresh' |> { value => '1' }
  
 
 
 
  
the error always implicates inifile, and there's never an 'origin' in the message, as might happen from lib/puppet/pops/loaders/base_loader.rb:123:  
 
 
 
 
    
 
 
   def fail_redefine(entry)  
 
 
 origin_info = entry.origin ? _("Originally set %{original}.") % { original: origin_label(entry.origin) } : _("Set at unknown location")  
 
 
 raise ArgumentError, _("Attempt to redefine entity '%{name}'. %{origin_info}") % { name: entry.typed_name, origin_info: origin_info }  
 
 
   end
  
 
 
 
  
it's using inifile 2.2.2 - the generated type definition for this type doesn't have any obvious wackiness (no composite namevars, procs in :name, etc) 
 Since this was a new problem that came in after an upgrade, I'm suggesting turning off the generation of type 

Jira (PUP-9202) Prepare release announcement (Puppet Platform 6.0.2)

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9202  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Prepare release announcement (Puppet Platform 6.0.2)   
 

  
 
 
 
 

 
 I'd like to see us default to publicly visible communication for these wherever possible, so both internal and external should say "puppet-dev Google group".  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8002  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Attempt to redefine entity" caused by using a resource collector
 

  
 
 
 
 

 
 Thomas Hallgren when you say "this needs to happen"... does that mean the change you linked to needs to go into additional places? since that PR seems to be merged and released.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3122) It's time we wrote a more usable no cert found warning!

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-3122  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: It's time we wrote a more usable no cert found warning!   
 

  
 
 
 
 

 
 this could absolutely go into any patch release.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9174) 50% chance system crash on puppet apply

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9174  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 50% chance system crash on puppet apply   
 

  
 
 
 
 

 
 David Hodgkinson This is truly a bizarre problem. I've never seen this before, and I'm pretty sure if there was a widespread problem where running puppet caused kernel panics that we would have heard about it previously.  The stack trace unfortunately just shows system calls and not the offending Puppet/Ruby code that's triggering the problem. Can you create a minimal reproducing manifest and run truss -f puppet apply file.pp to get more info about what's happening? Can you upgrade the kernel on one host and see if it fixes the problem...?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9174) 50% chance system crash on puppet apply

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson assigned an issue to David Hodgkinson  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9174  
 
 
  50% chance system crash on puppet apply   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Assignee: 
 David Hodgkinson  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9075) File type "replace => false" doesn't allow to remove the file if "ensure => absent"

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson assigned an issue to Vincent Lours  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9075  
 
 
  File type "replace => false" doesn't allow to remove the file if "ensure => absent"   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Assignee: 
 Vincent Lours  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9075) File type "replace => false" doesn't allow to remove the file if "ensure => absent"

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: File type "replace => false" doesn't allow to remove the file if "ensure => absent"   
 

  
 
 
 
 

 
 I think this is happening because of this check in lib/puppet/type/file/ensure.rb  
 
 
 
 
 # We have to treat :present specially, because it works with any  
 
 
 # type of file.  
 
 
 def insync?(currentvalue)  
 
 
   unless currentvalue == :absent or resource.replace?  
 
 
 return true  
 
 
   end  
 
 
    
 
 
   if self.should == :present  
 
 
 return !(currentvalue.nil? or currentvalue == :absent)  
 
 
   else  
 
 
 return super(currentvalue)  
 
 
   end  
 
 
 end
  
 
 
 

Jira (PUP-7582) Make attempt to export or virtualize a class an error

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-7582  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make attempt to export or virtualize a class an error   
 

  
 
 
 
 

 
 I think we're out of time on this one and it seems very low risk to leave it. I'm just gonna close/wontfix.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6165) it should not be possible to disable manifest ordering

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-6165  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: it should not be possible to disable manifest ordering   
 

  
 
 
 
 

 
 +1 to making this the only option; we made the ordering algorithm pluggable in https://projects.puppetlabs.com/issues/18508 , theoretically to allow different algorithms like a "fuzzer" random order. But nobody ever used this AFAIK and I agree with RI that it'd be good to have a guarantee that it's always on in Puppet 6 and above.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8094  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lookup ignores environment from the classifier when using rule with trusted facts   
 

  
 
 
 
 

 
 The user need for lookup is to simulate, as closely as possible, the values that a node will get when a catalog is compiled for it. Therefore, lookup should behave as similar to the catalog compilation data flow as possible – including the fact that the ENC would be authoritative for the environment. Am I missing something?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8094  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lookup ignores environment from the classifier when using rule with trusted facts   
 

  
 
 
 
 

 
 Moving back to Ready for Eng, unless there are further design questions from Thomas Hallgren or Henrik Lindberg - is there a clear path to implementation now?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7600) Deprecate built-in LDAP Node Terminus

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-7600  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deprecate built-in LDAP Node Terminus   
 

  
 
 
 
 

 
  Thorsten Schlump Can you use the regular ENC terminus, and have an external program call out to LDAP, maybe which reuses the code as it is today? The main problem with having the LDAP terminus in core is that it implies support/testing/bugfix guarantees that we just don't have in place.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6964  
 
 
  Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Fix Version/s: 
 PUP 5.y  
 
 
Fix Version/s: 
 PUP 6.0.0  
 
 
Fix Version/s: 
 PUP 5.5.7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6953) Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6953  
 
 
  Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Fix Version/s: 
 PUP 5.5.7  
 
 
Fix Version/s: 
 PUP 6.0.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6953) Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6953  
 
 
  Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Fix Version/s: 
 PUP 6.0.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6953) Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6953  
 
 
  Puppet should give a more direct error when it can't find a 4.x function because of a missing module dependency
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Fix Version/s: 
 PUP 5.5.7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (FACT-1870) Stdout in facts invalidates formatted output (yaml/json)

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  FACT-1870  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stdout in facts invalidates formatted output (yaml/json)   
 

  
 
 
 
 

 
 FWIW I confirmed that using the Facter.error helper method in the rescue block provides clean STDOUT/STDERR separation - So with the fact below, facter -p -j | jq . works even with the error-generating output. The fact that these helper methods and best practice is folklore is a problem, which recent doc updates will help address, but it needs more developer-centric attention.  
 
 
 
 
 Facter.add('test') do  
 
 
   confine :kernel => 'Linux'  
 
 
   begin  
 
 
 test = 'nomatch'  
 
 
 test = Facter.value(:doesntexist).strip()  
 
 
 setcode { test }  
 
 
   rescue Exception => ex  
 
 
 Facter.error "#{File.basename(__FILE__)} - ruby fact threw an exception: #{ex}"  
 
 
   end  
 
 
 end
  
 
 
 
   
 
 
 
 
  eric@cloudline> facter -j --custom-dir ~/.puppetlabs/etc/facter/lib 

Jira (PUP-5934) Updated fact values should be submitted after each Puppet run

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-5934  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Updated fact values should be submitted after each Puppet run   
 

  
 
 
 
 

 
 Greg Dubicki that'd be awesome!   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2983) Environment not updated via ENC if obsolete Environment in agents puppet.conf

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-2983  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Environment not updated via ENC if obsolete Environment in agents puppet.conf   
 

  
 
 
 
 

 
 This was the oldest bug but most of the work is tracked under PUP-6802  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9021) [Resource Type: service][Enhancement] Allow a Systemd service to be reload from a notify instead of restart

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-9021  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [Resource Type: service][Enhancement] Allow a Systemd service to be reload from a notify instead of restart   
 

  
 
 
 
 

 
 Good idea. This is a duplicate of an old ticket, so I'll link this and close it as a duplicate so we can track your design suggestion. Check out PUP-1054 for the previous discussion on this enhancement request.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8997) Deprecate Faces related to CA and certificate handling

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8997  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deprecate Faces related to CA and certificate handling   
 

  
 
 
 
 

 
 Yes because that will give people on the 5.x LTS series notice of something that will change when they upgrade  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8997) Deprecate Faces related to CA and certificate handling

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8997  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deprecate Faces related to CA and certificate handling   
 

  
 
 
 
 

 
 IMO it's OK for puppet cert to error with a message that shows how to do the top 3-5 common use cases with the new command line, as long as there are direct equivalents. If we don't have functionality in the new CLI that maps to the most common uses of puppet cert it ought to stay with a deprecation warning. I think that "top N" is probably: 
 
puppet cert sign - (CA) sign a pending request 
puppet cert generate - (Client/CA) to make a new private key and cert for hosts, especially infrastructure hosts that need subjectAltNames and can't be autosigned 
puppet cert list --all - (CA) to show the inventory of pending certificate requests (yes this is obnoxious) 
puppet cert list - (CA) to show already signed certs in preparation for revoking them 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more 

Jira (PUP-6521) Add the ability to describe Data Type for a Resource Param

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-6521  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add the ability to describe Data Type for a Resource Param   
 

  
 
 
 
 

 
 If I understand this correctly, I don't think it's needed or desirable.  Is this saying that a module author would need to define, for every parameter / property, a Puppet type in the ruby lib/puppet/type/foo.rb for native types, or in Puppet code (somewhere??) for defined types.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8942) Support issuing certificates with IP Address Subject Alternative Names

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8942  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support issuing certificates with IP Address Subject Alternative Names   
 

  
 
 
 
 

 
 Maggie Dreyer that'd be my preference, yes - otherwise it's a hard break for existing tooling  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3262) By default, the cadir should be separated from the ssldir

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-3262  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: By default, the cadir should be separated from the ssldir   
 

  
 
 
 
 

 
 Maggie Dreyer Hm, I feel like we need to respect the previous setting - the goal is to avoid a hard break for sites who are upgrading, and I think that includes the case where they've relocated the ssl dir via setting.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3834) remove webrick/rack support from Puppet

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-3834  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: remove webrick/rack support from Puppet   
 

  
 
 
 
 

 
 i think you could probably still do jruby vs mri testing with the puppet compile face, no?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8908) Resource status of "failed_to_restart" is not included in reports for individual resources

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8908  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Resource status of "failed_to_restart" is not included in reports for individual resources   
 

  
 
 
 
 

 
 I think we've been pretty comfortable updating the report version field independent of feature releases in the past (it is independently versioned with a monotonically increasing number IIRC). Can we pull this up the backlog for a 5.5.x so it will make it into the LTS?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8908) Resource status of "failed_to_restart" is not included in reports for individual resources

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8908  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Resource status of "failed_to_restart" is not included in reports for individual resources   
 

  
 
 
 
 

 
 Jacob Helwig this feels like a bugfix that could be delivered in a patch release without changing public behaviour. Does that sound right?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3834) remove webrick/rack support from Puppet

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-3834  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: remove webrick/rack support from Puppet   
 

  
 
 
 
 

 
 Trevor Vaughan having two network stacks and server-side runtimes is confusing and duplicative. Only one of them is actually supported in product, so removing webrick reduces a massive surface area for bugs that nobody is paying to fix. Sorry if that sounds mercenary, but it's the truth. Last time we talked about this a couple of years ago, an easy workflow for setting up a standalone server for testing was really important, so we held off on actually removing this until the containerized server stack was ready to go - which provides an environment that actually reflects what you're going to be running in production.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8901) Puppet5 server does not work with Puppet4 termini

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8901  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet5 server does not work with Puppet4 termini   
 

  
 
 
 
 

 
 you can't have mixed major versions among puppet db/server/agent (agent package installed on master, i mean - you can have older agents checking in to newer masters, of course). if the docs don't explicitly call that out they ought to.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3262) By default, the cadir should be separated from the ssldir

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-3262  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: By default, the cadir should be separated from the ssldir   
 

  
 
 
 
 

 
 Justin Stoller and I talked through this; a bit more guidance: 
 
the new CA dir ought to be under /etc/puppetlabs/puppetserver/ca, though the location should still be relocatable via a puppetserver.conf setting 
new installations should use that by default; existing installations should look in the old /etc/puppetlabs/puppet/ssl/ca directory and use that without modification if it exists (i.e. do not try to auto-migrate people's CA certs. that path lies madness!) 
the CLI tool from SERVER-2162 ought to provide an affordance for people to migrate an existing CA (whether single root+intermediate combo or root-only) from the old setup into a root+intermediate combo in the new location 
if we migrate it should also bring over the old CRL 
the implications on PE installations, both new and upgrades, need to be considered as part of this work (but under separate tickets) 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 

Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-7407  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add deprecation warning to Puppet::Util.absolute_path?   
 

  
 
 
 
 

 
 It looked like the best idea was to reimplement it behind the scenes so it's not using its own implementation but the public method signature doesn't change  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7600) Deprecate built-in LDAP Node Terminus

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-7600  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deprecate built-in LDAP Node Terminus   
 

  
 
 
 
 

 
 Kris go for it  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8710) Smarter cached catalogs

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8710  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Smarter cached catalogs   
 

  
 
 
 
 

 
 this doesn't feel like a Deferred problem to me, and I don't think it ought to be added on the agent directly. It's more related to the concept of event-driven infrastructure, where the input event is async facts submission (now possible with PUP-7779) on facts that the adminstrator cares about, the condition is the threshold management (subject to hysteresis, as henrik notes, hold-down is a key property of event-response frameworks), and the action is to trigger a fresh puppet run invalidating the local cache. 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-532) (#22719) Allow exec to runas different user on windows

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-532  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: (#22719) Allow exec to runas different user on windows   
 

  
 
 
 
 

 
   Josh Cooper this has come up again recently (see PUP-8395) and I'm wondering if you can explain this comment a bit further: 

  That said it can be worked around using an exec resource, e.g. runas.exe, psexec.exe 
 Could this be implemented as requested?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8711) Implement Agent Functions to support secret lookups at catalog application time

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8711  
 
 
  Implement Agent Functions to support secret lookups at catalog application time   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Summary: 
 Implement Agent -side functions  Functions  to support secret lookups at catalog application time  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8711) Implement Agent-side functions to support secret lookups at catalog application time

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8711  
 
 
  Implement Agent-side functions to support secret lookups at catalog application time   
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/10 4:17 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Sorenson  
 

  
 
 
 
 

 
 Many modern infrastructures make use of key-value stores like Conjur by CyberArk, Consul and Vault by Hashicorp, or Apache Zookeeper. These services keep track of rapidly-changing information like the list of servers currently active in an application pool as well as provide a central, access-controlled distribution point for sensitive data like access tokens, login credentials, and encryption keys. This epic tracks work towards a feature with the working title of "Agent Lookups", which provides a natural, intuitive interface to these services. The agent consults the service as it applies the catalog, providing credentials if needed, and injects the result of the lookup into the appropriate place on the host.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

Jira (PUP-8673) Puppet 5.5.1 should not have changed the Ruby deprecations - deprecations should be introduced in a new minor version

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson assigned an issue to Eric Sorenson  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8673  
 
 
  Puppet 5.5.1 should not have changed the Ruby deprecations - deprecations should be introduced in a new minor version   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Assignee: 
 Eric Sorenson  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8673) Puppet 5.5.1 should not have changed the Ruby deprecations - deprecations should be introduced in a new minor version

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8673  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet 5.5.1 should not have changed the Ruby deprecations - deprecations should be introduced in a new minor version   
 

  
 
 
 
 

 
 You are technically correct (the best kind of correct!). Read on in the same paragraph though: 
 
Before you completely remove the functionality in a new major release there should be at least one minor release that contains the deprecation so that users can smoothly transition to the new API.
 There will be more 5.x releases before 6.x removes this, and it seemed better to get the warnings in early rather than wait for a 5.6.0 to introduce them, or to call this release 5.6.0 solely due to the inclusion of a new deprecation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8591) Actually delete webrick

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8591  
 
 
  Actually delete webrick   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Summary: 
 [SPIKE] Investigate removing Actually delete  webrick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8639) need seamless way to replace expiring CA certificate

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8639  
 
 
  need seamless way to replace expiring CA certificate   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 

  
 
 
 
 

 
 What realistic option does a Puppet open source site have if the expiration on the CA master certificate is approaching, and one wants to smoothly transition to a new CA master certificate?The only official documentation I can find that comes close to this is the following: [ https://puppet.com/docs/puppet/5.5/ssl_regenerate_certificates.html ] But that procedure is describing an apocalypse-level security event where all certificates must be treated as untrustworthy and discarded.There is this: [ https://forge.puppet.com/puppetlabs/certregen ] …but that module hasn't been updated in almost a year, and  is incompatible  doesn't express compatibility  with Puppet 5 , because Puppet 5 removed {{puppet certregen}} and replaced it with… nothing, as far as I can tell. The only potential solution I can see is this: [ https://blog.flyingcircus.io/2017/09/01/how-to-renew-puppet-ca-and-server-certificates-in-place/ ] Perhaps PE already has a smooth way to do this, but there needs to be a smooth way to do this for Puppet open source as well, without sending sites running open source scurrying to random third-party blog posts.I realize this is both a very unsexy and very challenging issue to solve, but for the sites that need to solve it… it's a DEFCON 1 event.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
   

Jira (PUP-8639) need seamless way to replace expiring CA certificate

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8639  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: need seamless way to replace expiring CA certificate   
 

  
 
 
 
 

 
 James Ralston thanks for the report - the certregen module is indeed the right way to go here, it just needs some love and attention. I've put up a PR to bring it into "modern" puppet land, with support for Puppet 5 and some fixes that would have prevented it from working correctly: https://github.com/puppetlabs/puppetlabs-certregen/pull/43 Can you try it out and make sure it works for you? I'll get a blog post up on the official Puppet blog in the next couple of weeks - the code itself is really good work, we just took our eye off it before getting to the "waving banners and flags" promotional bit.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8639) need seamless way to replace expiring CA certificate

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson assigned an issue to Eric Sorenson  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8639  
 
 
  need seamless way to replace expiring CA certificate   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Assignee: 
 Eric Sorenson  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8639) need seamless way to replace expiring CA certificate

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8639  
 
 
  need seamless way to replace expiring CA certificate   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Team: 
 Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8638) Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc...

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8638  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet Compilation should fail if code is included outside of class definitions / node definitions / etc...   
 

  
 
 
 
 

 
 Isn't this a dup of PUP-1434?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8566) "puppet config print" should only emit diagnostic info when run with verbose or higher

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8566  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "puppet config print" should only emit diagnostic info when run with verbose or higher   
 

  
 
 
 
 

 
 Kris Bosland the subject header now accurately reflects acceptance criteria: '"puppet config print" should only emit diagnostic info when run with verbose or higher'  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8561) Augeas unable to handle escaped quotes within quotes

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8561  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Augeas unable to handle escaped quotes within quotes   
 

  
 
 
 
 

 
 Seems pretty low-risk to include in 5.5.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8492) Move the empty() function from stdlib to puppet

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8492  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Move the empty() function from stdlib to puppet   
 

  
 
 
 
 

 
 Sure, people could opt in to that if they were having problems. But (a) that syntax is all much more advanced than the if empty($foo) pattern, and (b) we can't find and fix all the instances of this, which are used in everything from other stdlib functions to the PE internal modules, so I don't think it's appropriate to mark it for a deprecation/removal.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8607) With certificate revocation set to false, why puppet still checks for crl? Error: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=er

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8607  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: With certificate revocation set to false, why puppet still checks for crl? Error: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=error: certificate verify failed   
 

  
 
 
 
 

 
 Rahul Srivastava it looks like you are using PE2017.3.0, can you please file a commercial support ticket through the customer portal for this issue? We will then be able to run the support scripts and get more information about your environment that will be difficult to do through the public bug tracker.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8611) Crontab gets erased after error during agent run

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8611  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Crontab gets erased after error during agent run   
 

  
 
 
 
 

 
 Two things - PE2016.4.2 is on an extremely old version of the puppet agent that lacks many bugfixes and needs to be updated. Also, this may be related to https://tickets.puppetlabs.com/browse/PUP-3656  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8492) Move the empty() function from stdlib to puppet

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8492  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Move the empty() function from stdlib to puppet   
 

  
 
 
 
 

 
 Henrik Lindberg Why deprecate the behaviour that empty on an undef variable is true? Is it going to change in the future? What is the workaround for people who currently use empty() to determine whether a variable is undef?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-7407  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add deprecation warning to Puppet::Util.absolute_path?   
 

  
 
 
 
 

 
 E - yes, only one version of each module which was latest as of the time i updated this corpus, maybe ~6 months ago  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-7407  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add deprecation warning to Puppet::Util.absolute_path?   
 

  
 
 
 
 

 
 No, I specifically excluded the vendored puppet implementations, the paths show only types and providers inside of modules. But I totally agree - I'm less concerned with keeping the implementation intact than keeping the method signature intact, which is what it looked like this ticket was doing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-4242  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add deprecation warnings for manifests declaring things in wrong namespace   
 

  
 
 
 
 

 
 Can this just be made to fail when --strict is on?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-7407  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add deprecation warning to Puppet::Util.absolute_path?   
 

  
 
 
 
 

 
 What does it hurt to leave this? I ask because unlike many of the deprecations in this epic, this one affects a large number of types and providers in the wild. A search through the forge corpus turned up:   
 
 
 
 
 ag --ignore spec --ignore stdlib --ignore vendor --ignore gem 'absolute_path\?' *  -l | wc -l  
 
 
 53
  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more 

Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8566  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "puppet config print" needs --quiet option to disable new (default) verbosity   
 

  
 
 
 
 

 
 IMO we should make this output only show up when you specify -verbose or -debug ; this preserves the previous behaviour but makes it easy to troubleshoot if you are getting results you don't expect.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2997) Logdest cannot be set in the puppet.conf

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2997  
 
 
  Logdest cannot be set in the puppet.conf   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Team: 
 Agent Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2997) Logdest cannot be set in the puppet.conf

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2997  
 
 
  Logdest cannot be set in the puppet.conf   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Sprint: 
 Platform Core Hopper  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-7582) Make attempt to export or virtualize a class an error

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-7582  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make attempt to export or virtualize a class an error   
 

  
 
 
 
 

 
 What is the downside of continuing the behavior as it is? Do people do this in the world right now, and if so, what problem are they trying to solve?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-2149) Deprecate implicit creation of symlinks when file ensure parameter is unknown

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2149  
 
 
  Deprecate implicit creation of symlinks when file ensure parameter is unknown   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 

  
 
 
 
 

 
 This manifest creates a bogus symlink. My contention is that it should reject the invalid attribute value and not create a symlink.{code} # [eric@cloudline]~%  puppet apply -e  '  " file { '/tmp/jenny': ensure => symlink, } "  Debug: Failed to load library 'selinux' for feature 'selinux' Notice: Compiled catalog for  breve  cloudline . wifi.puppetlabs.net localdomain  in environment production in 0. 12 02  seconds Debug: Creating default schedulesDebug: Using settings: adding file resource 'confdir': 'File[/etc/puppet]{:path=>"/etc/puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Failed to load library 'shadow' for feature 'libshadow'Debug: Puppet::Type::User::ProviderUseradd: file useradd does not existDebug: Failed to load library 'ldap' for feature 'ldap'Debug: Puppet::Type::User::ProviderLdap: feature ldap is missingDebug: Puppet::Type::User::ProviderPw: file pw does not existDebug: Puppet::Type::User::ProviderUser_role_add: file useradd does not existDebug: /User[puppet]: Provider directoryservice does not support features libuser; not managing attribute forcelocalDebug: Executing '/usr/bin/dscl . read /Users/puppet'Debug: Puppet::Type::Group::ProviderGroupadd: file groupadd does not existDebug: Failed to load library 'ldap' for feature 'ldap'Debug: Puppet::Type::Group::ProviderLdap: feature ldap is missingDebug: Puppet::Type::Group::ProviderPw: file pw does not existDebug: /Group[puppet]: Provider directoryservice does not support features libuser; not managing attribute forcelocalDebug: Executing '/usr/bin/dscl -plist . -list /Groups'Debug: Executing '/usr/bin/dscl -plist . -read /Groups/puppet'Debug: Using settings: adding file resource 'vardir': 'File[/var/lib/puppet]{:path=>"/var/lib/puppet", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'logdir': 'File[/var/lib/puppet/log]{:path=>"/var/lib/puppet/log", :mode=>"750", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'statedir': 'File[/var/lib/puppet/state]{:path=>"/var/lib/puppet/state", :mode=>"1755", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'rundir': 'File[/var/lib/puppet/run]{:path=>"/var/lib/puppet/run", :mode=>"755", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'libdir': 'File[/var/lib/puppet/lib]{:path=>"/var/lib/puppet/lib", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'Debug: Using settings: adding file resource 'certdir': 'File[/etc/puppet/ssl/certs]{:path=>"/etc/puppet/ssl/certs", :mode=>"755", 

Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8094  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lookup ignores environment from the classifier when using rule with trusted facts   
 

  
 
 
 
 

 
 Laura Macchi Henrik Lindberg Sorry, I missed the earlier question and just came across this during the CS Top 10 triage. To answer Henrik's question above, I strongly agree with Laura that lookup should as closely as possible mimic what the agent would receive, that is, it should treat the ENC as authoritative.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3647) Puppet stores files forever in state.yaml

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3647  
 
 
  Puppet stores files forever in state.yaml   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Sprint: 
 Platform Core Hopper  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8545) puppet 5/ruby 2.4 can't handle invalid plists

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8545  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet 5/ruby 2.4 can't handle invalid plists   
 

  
 
 
 
 

 
 (Because Jira is SOooOO awesome, only single line code samples can be formatted with double-curly braces. Multiline samples need to get wrapped in {code} tags)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8545) puppet 5/ruby 2.4 can't handle invalid plists

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8545  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet 5/ruby 2.4 can't handle invalid plists   
 

  
 
 
 
 

 
 Clay Caviness thanks for the report - what is the puppet code that triggers this situation? Are you managing the plist directly or is this through a service resource?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-6964  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency   
 

  
 
 
 
 

 
 This needs to get fixed in the 5.5.x series, or no one will be able to reasonably use 4.x functions in modules.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8290) Allow auto-conversion to Sensitive data type

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8290  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow auto-conversion to Sensitive data type   
 

  
 
 
 
 

 
 This came up with a customer yesterday. The root of their problem is that you cannot currently combine automatic parameter lookup with Sensitive[T] - casting a value in this way currently fails:  
 
 
 
 
 class myclass (  
 
 
 Sensitive $parameter = undef  
 
 
 ) {  
 
 
 notice("This parameter should be $sensitive")  
 
 
 }
  
 
 
 
  ... because everything that comes back from the hiera lookup is a string and thus fails type checking.  Henrik Lindberg I fear the Init[T] usage describes above is over-generalized and harder to understand than permitting coercion into Sensitive.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

Jira (PDB-3852) PuppetDB query nodes based on fact broken

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PDB-3852  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PuppetDB query nodes based on fact broken   
 

  
 
 
 
 

 
 Might be related?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-8470) Unable to modify local user group membership with forcelocal

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8470  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to modify local user group membership with forcelocal   
 

  
 
 
 
 

 
 I've just spent like 20 minutes trying to understand this problem and I'm starting to believe I'm not smart enough to really get it. There's always been an orthogonality to the user/group management split, because group membership can be both a property of the group and a property of each user in that group. The docs guidance says that you should use group resources just to create/remove groups, and manage group membership as a property of the user resources, except for some group providers like macOS and Windows which, as you note Melissa, have manages_members on them. I think this ought to be the exception. Group membership management should continue to primarily be the responsibility of the user resources. Therefore the problem case is when: 
 
forcelocal is true for the user 
system configuration points at a remote mechanism for group management. 
 Interestingly, the man page for usermod on RHEL says: 
 
 You may not add a user to a NIS or LDAP group. This must be performed on the corresponding server. 
 Similarly, if the username already exists in an external user database such as NIS or LDAP, useradd will deny the user account creation request.
 So maybe we just keep using usermod, and let the underlying system error out if that is an invalid configuration?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

Jira (PUP-7068) Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-7068  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml   
 

  
 
 
 
 

 
 Thomas Hallgren this came up from a user on irc today - what is the expected behaviour when the running process is the puppet master? They wanted to use relative paths to the datadir to avoid hardcoding the whole filesystem path, making the puppet/hiera setup more relocatable.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (BOLT-337) Nodes in inventory groups should accept "host:port" syntax

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-337  
 
 
  Nodes in inventory groups should accept "host:port" syntax   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/02/14 9:51 AM  
 
 
Environment: 
 When trying to use inventory files with docker containers, we ran into problems using this kind of syntax to address hosts. Each container has a different port that ssh is running on, but syntax like this didn't work:  
 
 
 
 
 groups:  
 
 
   - name: lab  
 
 
 nodes:  
 
 
 - node1:32768  
 
 
 - node2:32769  
 
 
 - node3:32770
  
 
 
 
  Instead this, much less untuitive syntax, was necessary:  
 
 
 
 
 groups:  
 
 
   - name: lab  
  

Jira (BOLT-318) I want to refer to inventory groups as targets

[Eric Sorenson (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  BOLT-318  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: I want to refer to inventory groups as targets   
 

  
 
 
 
 

 
 In working through this feature with the CS team yesterday, nearly everyone expected that a bareword argument to -nodes that matched a group name would target that group, and if there were no matches it would be treated as a hostname. Additional syntax could be used to disambiguate but the group thought if so, it should be some punctuation sigil, by analogy to the -nodes @file syntax to indicate loading from a file.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.