Jira (PUP-8539) Hiera trusted fact lookup

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Thomas Hallgren  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8539  
 
 
  Hiera trusted fact lookup   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Thomas Hallgren  
 

  
 
 
 
 

 
 
 

 
 
 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-8539) Hiera trusted fact lookup

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8539  
 
 
  Hiera trusted fact lookup   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Component/s: 
 CLI  
 
 
Component/s: 
 Hiera & Lookup  
 

  
 
 
 
 

 
 
 

 
 
 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-8539) Hiera trusted fact lookup

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8539  
 
 
  Hiera trusted fact lookup   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Fix Version/s: 
 HI 3.3.2  
 
 
Affects Version/s: 
 HI 3.3.2  
 
 
Component/s: 
 CLI  
 
 
Component/s: 
 CLI  
 
 
Key: 
 HI PUP - 590 8539  
 
 
Project: 
 Hiera Puppet  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  

Jira (PUP-8500) puppet lookup cli should support adding facts as arguments, not just from a file.

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Thomas Hallgren  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8500  
 
 
  puppet lookup cli should support adding facts as arguments, not just from a file.   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Thomas Hallgren  
 

  
 
 
 
 

 
 
 

 
 
 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-8499) puppet lookup cli, using --facts and --node simultaneously breaks

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Thomas Hallgren  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8499  
 
 
  puppet lookup cli, using --facts and --node simultaneously breaks   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Thomas Hallgren  
 

  
 
 
 
 

 
 
 

 
 
 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-8486) Warning for undefined variables is slow in jruby

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-8486  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
 Do you think it is worth making the change in hiera 3? It would need to catch the not-found and issue a warning or an error under the control of the strictness settings. (it would be yet another place where this takes place - there are two already; the one you linked to for the general case of logic not handling the throw, and one in the evaluator.  The places where this is handled are different in terms of the knowledge they have about the context and it is difficult to have them share an implementation - same thing with the hiera case. It could be an improvement though as hiera could provide information regarding the context in which it looks up the variable which I think is missing as it is 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-8439) Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8439  
 
 
  Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Release Notes Summary: 
 The data types Timespan and Timestamp incorrectly set the upper bounds to the same as lower bounds when created with a single parameter - that is T[x] was taken as T[x,x] instead of T[x, ]. This is now corrected.  
 
 
Release Notes: 
 Bug Fix  
 

  
 
 
 
 

 
 
 

 
 
 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-8494) Issue based errors are formatted too early and arguments are lost.

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8494  
 
 
  Issue based errors are formatted too early and arguments are lost.   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Release Notes: 
 Not Needed  
 

  
 
 
 
 

 
 
 

 
 
 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

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Release Notes Summary: 
 The {{empty()}} function has moved from stdlib to puppet, and now also supports answering if a {{Binary}} value is empty (has zero bytes).  Calling empty with an undef value, or with a numeric value is now also deprecated and will issue a warning.  
 

  
 
 
 
 

 
 
 

 
 
 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-7307) Tidy should support 'purge' or update file resource

2018-03-09 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-7307  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Tidy should support 'purge' or update file resource   
 

  
 
 
 
 

 
 Justin could you comment in the PR? The reference documentation is generated from the source code, so best to fix it there. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 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-6996) Puppet automatically creates the production environment with the incorrect permissions

2018-03-09 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6996  
 
 
  Puppet automatically creates the production environment with the incorrect permissions   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 5.5.0  
 
 
Fix Version/s: 
 PUP 5.y  
 

  
 
 
 
 

 
 
 

 
 
 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-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original

2018-03-09 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8493  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The differences between the vendored semantic_puppet and the original make it impossible to swap in the original   
 

  
 
 
 
 

 
 Thomas Hallgren once we unvendor the old semantic_puppet we won't be able to enable "lenient" semver. Do we need to deprecate that in PMT before we remove that ability in 6?  
 

  
 
 
 
 

 
 
 

 
 
 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-8477) selinux types are being set on every run

2018-03-09 Thread Melissa Stone (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8477  
 
 
  selinux types are being set on every run   
 

  
 
 
 
 

 
Change By: 
 Melissa Stone  
 
 
Release Notes Summary: 
 If selinux bindings are not available in puppet, we would try to manage a setting but not be able to read in what it was currently set as. This change makes it so that if we do not have selinux bindings, we don't try to check the current setting as we do not have access to it.  
 
 
Release Notes: 
 Bug Fix  
 

  
 
 
 
 

 
 
 

 
 
 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-1549) Build CFacter gems in Jenkins

2018-03-09 Thread Sean McDonald (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean McDonald updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1549  
 
 
  Build CFacter gems in Jenkins   
 

  
 
 
 
 

 
Change By: 
 Sean McDonald  
 
 
Sprint: 
 Platform OS  Ready for Eng.  Kanban  
 

  
 
 
 
 

 
 
 

 
 
 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-1549) Build CFacter gems in Jenkins

2018-03-09 Thread Sean McDonald (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean McDonald assigned an issue to Sean McDonald  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1549  
 
 
  Build CFacter gems in Jenkins   
 

  
 
 
 
 

 
Change By: 
 Sean McDonald  
 
 
Assignee: 
 Sean McDonald  
 

  
 
 
 
 

 
 
 

 
 
 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-8232) Re-add the puppet facts upload face and REST facts terminus

2018-03-09 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8232  
 
 
  Re-add the puppet facts upload face and REST facts terminus   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Release Notes Summary: 
 This restores the ability to upload facts to puppet server and masters, which is important for direct puppet workflows when agents always run off of cached catalogs and need an alternate mechanism to upload facts. It also updates the default legacy auth.conf to allow agents to only upload their own facts.  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 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-8477) selinux types are being set on every run

2018-03-09 Thread Eric Delaney (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Delaney commented on  PUP-8477  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: selinux types are being set on every run   
 

  
 
 
 
 

 
 Melissa Stone can you add release notes please?  
 

  
 
 
 
 

 
 
 

 
 
 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-8232) Re-add the puppet facts upload face and REST facts terminus

2018-03-09 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8232  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Re-add the puppet facts upload face and REST facts terminus   
 

  
 
 
 
 

 
 Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/a6cba646497dfd264506b789a66af522d2b1cdec  
 

  
 
 
 
 

 
 
 

 
 
 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 (PDB-3852) PuppetDB query nodes based on fact broken

2018-03-09 Thread Jeff Yarnell (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Yarnell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3852  
 
 
  PuppetDB query nodes based on fact broken   
 

  
 
 
 
 

 
Change By: 
 Jeff Yarnell  
 
 
Sprint: 
 Data Platform 2018- 03 04 - 28 11  
 

  
 
 
 
 

 
 
 

 
 
 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 (PDB-3856) PQL specifying both type and title for class makes pql not find existing class

2018-03-09 Thread Jeff Yarnell (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Yarnell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3856  
 
 
  PQL specifying both type and title for class makes pql not find existing class   
 

  
 
 
 
 

 
Change By: 
 Jeff Yarnell  
 
 
Sprint: 
 Data Platform 2018- 03 04 - 28 11  
 

  
 
 
 
 

 
 
 

 
 
 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-8441) Error datatype should support to_json

2018-03-09 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer commented on  PUP-8441  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error datatype should support to_json   
 

  
 
 
 
 

 
 Do you have a proposal for what the PAL methods for this would like? What methods would ruby objects have to implement to be serializable?  
 

  
 
 
 
 

 
 
 

 
 
 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-8477) selinux types are being set on every run

2018-03-09 Thread Eric Delaney (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Delaney commented on  PUP-8477  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: selinux types are being set on every run   
 

  
 
 
 
 

 
 merged to 5.5.x at https://github.com/puppetlabs/puppet/commit/dd8f95e6d2e7132d0d379de32dadfbdc2d284dd7  
 

  
 
 
 
 

 
 
 

 
 
 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-8487) Eliminate use of MethodHelper

2018-03-09 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8487  
 
 
  Eliminate use of MethodHelper   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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 (PDB-3873) Fix PDB 5.1 5.2 rspec for puppet changes around 2018-03-09i

2018-03-09 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3873  
 
 
  Fix PDB 5.1 5.2 rspec for puppet changes around 2018-03-09i   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Rob Browning  
 
 
Created: 
 2018/03/09 2:55 PM  
 
 
Fix Versions: 
 PDB 5.2.2  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rob Browning  
 

  
 
 
 
 

 
 Git bisect says the problem started with puppet: commit d2e6af6cf0d4745cd838184b50fde0f6e970cf7f (refs/bisect/bad) Author: Patrick Carlisle  Date: Thu Feb 15 12:27:36 2018 -0800  (maint) Optimize tags  There are a bunch of places where tags are merged from one object into another and we already know they are valid, so it's unnecessary to recheck them. Some code was already in place to reduce rechecking. This commit applies that change in more places.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

Jira (BOLT-348) Add automated tests of system packages

2018-03-09 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis assigned an issue to Nick Lewis  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-348  
 
 
  Add automated tests of system packages   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
Assignee: 
 Nick Lewis  
 

  
 
 
 
 

 
 
 

 
 
 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-8538) AIX user resource fails with new service packs

2018-03-09 Thread Jarret Lavallee (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jarret Lavallee moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8538  
 
 
  AIX user resource fails with new service packs   
 

  
 
 
 
 

 
Change By: 
 Jarret Lavallee  
 
 
Affects Version/s: 
 puppet-agent 5.3.5  
 
 
Affects Version/s: 
 PUP 4.10.10  
 
 
Affects Version/s: 
 PUP 5.3.5  
 
 
Key: 
 PA PUP - 1905 8538  
 
 
Project: 
 Puppet  Agent  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are 

Jira (PUP-8485) Cached failed confine lookups

2018-03-09 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8485  
 
 
  Cached failed confine lookups   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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-57) Download a file

2018-03-09 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-57  
 
 
  Download a file   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Assignee: 
 Michael Smith  
 

  
 
 
 
 

 
 
 

 
 
 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-373) Update Puppet for new core functions

2018-03-09 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-373  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update Puppet for new core functions   
 

  
 
 
 
 

 
 Can we instead unvendor Puppet?  
 

  
 
 
 
 

 
 
 

 
 
 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 (PDB-3830) Command Queue Grows Steadily Over Time not related to load

2018-03-09 Thread Nick Walker (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Walker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3830  
 
 
  Command Queue Grows Steadily Over Time not related to load   
 

  
 
 
 
 

 
Change By: 
 Nick Walker  
 
 
Release Notes Summary: 
 PuppetDB  should  now correctly  account for incoming commands that cannot be processed in  reduces  the  command  queue  depth metric  size when a malformed message is submitted to the queue .  Previously  they were ignored  if you submitted a message that PuppetDB discards ,  which could cause  the  depth to appear to grow over time  command queue would increase when the message came in and would not reduce when the message was discarded .     
 

  
 
 
 
 

 
 
 

 
 
 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-8267) Rewrite acceptance rake tasks to leverage beaker subcommand support

2018-03-09 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8267  
 
 
  Rewrite acceptance rake tasks to leverage beaker subcommand support   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Release Notes: 
 Not Needed  
 

  
 
 
 
 

 
 
 

 
 
 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-8494) Issue based errors are formatted too early and arguments are lost.

2018-03-09 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey commented on  PUP-8494  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Issue based errors are formatted too early and arguments are lost.   
 

  
 
 
 
 

 
 Thomas Hallgren please add release notes for this issue, if needed. Thanks!    
 

  
 
 
 
 

 
 
 

 
 
 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

2018-03-09 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey commented on  PUP-8492  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 Henrik Lindberg please add release notes for this issue, if needed. Thanks!   
 

  
 
 
 
 

 
 
 

 
 
 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-8439) Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit

2018-03-09 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey commented on  PUP-8439  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default upper limit of Timestamp and Timespan data types is incorrectly set equal to lower limit   
 

  
 
 
 
 

 
 Thomas Hallgren please add release notes for this issue, if needed. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 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-8232) Re-add the puppet facts upload face and REST facts terminus

2018-03-09 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8232  
 
 
  Re-add the puppet facts upload face and REST facts terminus   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 Eric Delaney Josh Cooper  
 

  
 
 
 
 

 
 
 

 
 
 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-8498) No title provided and "foo" is not a valid resource reference

2018-03-09 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8498  
 
 
  No title provided and "foo" is not a valid resource reference   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 4.10.z  
 

  
 
 
 
 

 
 
 

 
 
 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-8498) No title provided and "foo" is not a valid resource reference

2018-03-09 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8498  
 
 
  No title provided and "foo" is not a valid resource reference   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sub-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-8498) No title provided and "foo" is not a valid resource reference

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-8498  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No title provided and "foo" is not a valid resource reference   
 

  
 
 
 
 

 
 The error occurs when the validator is asking if the given value is a resource. It errors out prematurely instead of getting the higher quality error message from the validator. This is an easy fix for the logic around line 35 (if it errors when getting the resource with the specific error) it should take that as a not found. Alternatively it should call "extract type and title" on its own to not be exposed to other types of errors (which we do want to surface).  
 

  
 
 
 
 

 
 
 

 
 
 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-8498) No title provided and "foo" is not a valid resource reference

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Henrik Lindberg  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8498  
 
 
  No title provided and "foo" is not a valid resource reference   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Henrik Lindberg  
 

  
 
 
 
 

 
 
 

 
 
 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-8486) Warning for undefined variables is slow in jruby

2018-03-09 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-8486  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
 https://github.com/puppetlabs/puppet/blob/master/lib/puppet/parser/scope.rb#L525-L544 If you're not in strict mode it doesn't fail. The exception gets caught here and turned into a warning, which I think is consistent with non-strict mode in general.  
 

  
 
 
 
 

 
 
 

 
 
 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-8498) No title provided and "foo" is not a valid resource reference

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8498  
 
 
  No title provided and "foo" is not a valid resource reference   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Affects Version/s: 
 PUP 5.3.3  
 
 
Affects Version/s: 
 PUP 4.10.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-8498) No title provided and "foo" is not a valid resource reference

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8498  
 
 
  No title provided and "foo" is not a valid resource reference   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Fix Version/s: 
 PUP 5.5.0  
 
 
Fix Version/s: 
 PUP 5.3.z  
 
 
Fix Version/s: 
 PUP 4.10.z  
 

  
 
 
 
 

 
 
 

 
 
 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-8498) No title provided and "foo" is not a valid resource reference

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8498  
 
 
  No title provided and "foo" is not a valid resource reference   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 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-8498) No title provided and "foo" is not a valid resource reference

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-8498  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No title provided and "foo" is not a valid resource reference   
 

  
 
 
 
 

 
 This comes from the catalog validation - I ran the relevant part of the example with --trace and this is what I got:  
 
 
 
 
 Error: No title provided and "xyz" is not a valid resource reference on node henrik2  
 
 
 /Users/henrik/git/puppet/lib/puppet/resource.rb:592:in `extract_type_and_title'  
 
 
 /Users/henrik/git/puppet/lib/puppet/resource.rb:577:in `type_and_title'  
 
 
 /Users/henrik/git/puppet/lib/puppet/resource/catalog.rb:371:in `resource'  
 
 
 /Users/henrik/git/puppet/lib/puppet/parser/compiler/catalog_validator/relationship_validator.rb:35:in `block in validate_relationship'  
 
 
 /Users/henrik/git/puppet/lib/puppet/parser/compiler/catalog_validator/relationship_validator.rb:33:in `each'  
 
 
 /Users/henrik/git/puppet/lib/puppet/parser/compiler/catalog_validator/relationship_validator.rb:33:in `validate_relationship'  
 
 
 /Users/henrik/git/puppet/lib/puppet/parser/compiler/catalog_validator/relationship_validator.rb:11:in `block (2 levels) in validate'
  
 
 
 
  So, it looks like a validation problem after compilation.  
 

  
 
 
 
 

 
 
 

Jira (PUP-8513) Cannot add a resource parameter, when a default resource declaration already defines this param

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-8513  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add a resource parameter, when a default resource declaration already defines this param   
 

  
 
 
 
 

 
 The first example uses a resource default _expression_ and then a resource override _expression_. The override of the resource occurs outside the scope of the containing class of the resource (and is also not within a scope that inherits from the declaring class. That override is not legal in the puppet language. Hence my question if this ever worked - I think you are simply encountering a valid error and that you need to do what you intended some other way.  Just in case - this is the resource override _expression_:  
 
 
 
 
   File['/tmp/puppet-test']{  
 
 
 ignore => '*.bak2',  
 
 
   }
  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

   

Jira (PUP-8513) Cannot add a resource parameter, when a default resource declaration already defines this param

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-8513  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add a resource parameter, when a default resource declaration already defines this param   
 

  
 
 
 
 

 
 Is this something that has worked before? If so, in which version?  
 

  
 
 
 
 

 
 
 

 
 
 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-8513) Cannot add a resource parameter, when a default resource declaration already defines this param

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Peter Meier  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8513  
 
 
  Cannot add a resource parameter, when a default resource declaration already defines this param   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Peter Meier  
 

  
 
 
 
 

 
 
 

 
 
 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

2018-03-09 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3262  
 
 
  By default, the cadir should be separated from the ssldir   
 

  
 
 
 
 

 
Change By: 
 Charlie Sharpsteen  
 
 
Affects Version/s: 
 PUP 4.10.10  
 
 
Affects Version/s: 
 PUP 5.4.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 (BOLT-348) Add automated tests of system packages

2018-03-09 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-348  
 
 
  Add automated tests of system packages   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Sprint: 
 Bolt  Ready for Grooming  Kanban  
 

  
 
 
 
 

 
 
 

 
 
 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-348) Add automated tests of system packages

2018-03-09 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-348  
 
 
  Add automated tests of system packages   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 We should  ideally have some basic testing of built system packages  create a new acceptance presuite  that  gets run before releasing them. This could potentially be part of  installs a bolt os package and runs  the  Orchestrator  existing acceptance  tests  against it .  Tests should cover: * Running bolt command/task/script/file upload * Running bolt plan * Running bolt [task|plan] show We should  re- run  these tests as part of  the  same acceptance suite we use (  packaging pipeline or whereever else best maps to  validate the gem) with packages  existing pipeline patterns .  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (BOLT-167) I want to pass a pql query instead of a list of nodes.

2018-03-09 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer assigned an issue to Alex Dreyer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-167  
 
 
  I want to pass a pql query instead of a list of nodes.   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Assignee: 
 Nick Lewis Alex Dreyer  
 

  
 
 
 
 

 
 
 

 
 
 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-1832) Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone.

2018-03-09 Thread Neil Binney (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Neil Binney created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1832  
 
 
  Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 facterdebug.txt, truss-output.txt  
 
 
Created: 
 2018/03/09 8:47 AM  
 
 
Environment: 
 Publisher: solaris  Version: 0.5.11  Build Release: 5.11  Branch: 0.175.3.29.0.4.0  Puppet: 4.10.4  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Neil Binney  
 

  
 
 
 
 

 
 When running facter in a zone following error occurs; 2018-03-07 12:22:40.806413 DEBUG puppetlabs.facter - resolving virtualization facts. 2018-03-07 12:22:40.806612 DEBUG puppetlabs.facter - resolving ldom facts. 2018-03-07 12:22:40.806754 DEBUG puppetlabs.facter - resolving processor facts. 2018-03-07 12:22:40.807161 DEBUG leatherman.execution:92 - executing command: /sbin/uname -p 2018-03-07 12:22:40.809843 DEBUG | - sparc 2018-03-07 12:22:40.810153 DEBUG leatherman.execution:556 - process exited with status code 0. terminate called after throwing an instance of 'facter::util::solaris::kstat_exception' what(): kstat_read failed: Permission denied (13) facter runs correctly on the global zone. 3530/1: 0.184177 ioctl(7, KSTAT_IOC_READ, "pic3") = 1410238  3530/1: 0.184229 ioctl(7, KSTAT_IOC_READ, "counters") Err#13 EACCES  3530/1: 0.185395 fstat64(2, 0xFFBFDF58) = 0  3530/1: 0.185468 write(2, " t e r m i n a t e c a".., 48) = 48  3530/1: 0.185546 write(2, " f a c t e r : : u t i l".., 38) = 38  3530/1: 0.185622 write(2, " '\n", 2) = 2  3530/1: 0.185795 write(2, " w h a t ( ) : ", 11) = 11  3530/1: 0.185870 write(2, " k s t a t _ r e a d f".., 41) = 41  3530/1: 0.185955 write(2, "\n", 1) = 1  3530/1: 0.186056 sigaction(SIGABRT, 0x, 0xFFBFE250) = 0  3530/1: 0.186107 sigaction(SIGABRT, 0xFFBFE100, 0xFFBFE1A0) = 0  3530/1: 0.186140 lwp_sigmask(SIG_SETMASK, 0x, 0x, 

Jira (PDB-3853) Release PuppetDB 5.2.z(Platform 5.5.0 - 2018-03-14)

2018-03-09 Thread Jeff Yarnell (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Yarnell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3853  
 
 
  Release PuppetDB 5.2.z(Platform 5.5.0 - 2018-03-14)   
 

  
 
 
 
 

 
Change By: 
 Jeff Yarnell  
 

  
 
 
 
 

 
 Release PuppetDB in preparation for the Puppet Platform 5.5.0 release [ https://confluence.puppetlabs.com/display/PM/Puppet+Platform+5.5.0 ]*Stop Ship (code freeze):* 14-Mar*Ready to Ship (PDB release created & ready for release)*: Monday 19-Mar  
 

  
 
 
 
 

 
 
 

 
 
 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-371) Docs for installing Bolt from packages

2018-03-09 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-371  
 
 
  Docs for installing Bolt from packages   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Fix Version/s: 
 BOLT 0.17.1  
 

  
 
 
 
 

 
 
 

 
 
 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-8518) yum check-update does not support --config (install_options)

2018-03-09 Thread Raymond Pettersen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Raymond Pettersen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8518  
 
 
  yum check-update does not support --config (install_options)   
 

  
 
 
 
 

 
Change By: 
 Raymond Pettersen  
 
 
Priority: 
 Normal Major  
 

  
 
 
 
 

 
 
 

 
 
 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 (PDB-3843) Error: /Stage[main]/Postgresql::Server::Config/Concat[/var/lib/pgsql/9.6/data/pg_hba.conf]/Concat_file[/var/lib/pgsql/9.6/data/pg_hba.conf]: Failed to generate additional resources usi

2018-03-09 Thread Ken Barber (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ken Barber commented on  PDB-3843  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error: /Stage[main]/Postgresql::Server::Config/Concat[/var/lib/pgsql/9.6/data/pg_hba.conf]/Concat_file[/var/lib/pgsql/9.6/data/pg_hba.conf]: Failed to generate additional resources using 'eval_generate': comparison of Array with Array failed   
 

  
 
 
 
 

 
 harish could you please provide: 
 
The full code for how you applied the puppetdb module, what instructions did you follow, and can you show me the code snippet for how you applied it? 
What is the full error, if you try  
 
 
 
 
 puppet agent -t --trace  
 
 
 
  when running the agent it should show a full stack trace 
 Thanks.  
 

  
 
 
 
 

 
 
 

 
 
 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-8537) Validator incorrectly reports result of regexp match as being forgotten

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8537  
 
 
  Validator incorrectly reports result of regexp match as being forgotten   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Thomas Hallgren  
 

  
 
 
 
 

 
 
 

 
 
 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

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-8290  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow auto-conversion to Sensitive data type   
 

  
 
 
 
 

 
 Note, we have not implemented auto-cast for Init[T], the logic will need to instantiate the T from the given value. We did not want to implement auto-casting for all of the reasons this ends up introducing problems in other programming languages. My earlier comment was made before we came to that conclusion. There is another option here - that we add type-conversion to lookup_options. You would then specify which data type you want to convert to, and possibly give the arguments / formats required. That way all rich data types can be instantiated (most likely things like timestamps and versions) and be type checked. What you would specify in lookup options would be either a single value data type for the key convert_to, or an array with the data type being the first argument. Example - cast to Sensitive  
 
 
 
 
 lookup_options:  
 
 
   myclass::parameter:  
 
 
 convert_to: 'Sensitive'
  
 
 
 
  Example - cast to a Timestamp with format 'HH:MM'  
 
 
 
 
 lookup_options:  
 
 
   myclass::start_time:  
 
 
 convert_to:   
 
 
   - 'Timestamp'  
 
 
   - 'HH:MM'
  
 
 
 
  I would rather implement that as it is general. What do you think Eric Sorenson?  

Jira (PUP-8486) Warning for undefined variables is slow in jruby

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-8486  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
 Irrespective of my earlier comment, it would naturally be better if the hiera implementation was explicit about "not found variable", but it should probably then also check if in strict mode for missing variables etc. I am however nervous about making any changes to hiera 3 due to lack of test coverage.  
 

  
 
 
 
 

 
 
 

 
 
 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-8486) Warning for undefined variables is slow in jruby

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-8486  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Warning for undefined variables is slow in jruby   
 

  
 
 
 
 

 
 Well, shouldn't those fail in that case? And if so, does it really matter if it fails a bit more slowly? Or is there a rescue higher up that turns the error into some kind of "not found"?  
 

  
 
 
 
 

 
 
 

 
 
 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-8537) Validator incorrectly reports result of regexp match as being forgotten

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8537  
 
 
  Validator incorrectly reports result of regexp match as being forgotten   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Sub-team: 
 Language  
 
 
Team: 
 Platform Core  
 
 
Sprint: 
 Platform Core KANBAN  
 

  
 
 
 
 

 
 
 

 
 
 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-8537) Validator incorrectly reports result of regexp match as being forgotten

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8537  
 
 
  Validator incorrectly reports result of regexp match as being forgotten   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Labels: 
 Language  
 

  
 
 
 
 

 
 
 

 
 
 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-8537) Validator incorrectly reports result of regexp match as being forgotten

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8537  
 
 
  Validator incorrectly reports result of regexp match as being forgotten   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Release Notes Summary: 
 A sequence such as:{code:puppet}'cdf' =~ /^([a-z])(.*)/notice($2){code}Would result in an error that the match _expression_ had no effect. This was caused by validation not considering that numeric match variables may be set as a side-effect of evaluating the match. This is not corrected.  
 
 
Release Notes: 
 Bug Fix  
 

  
 
 
 
 

 
 
 

 
 
 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-8537) Validator incorrectly reports result of regexp match as being forgotten

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Thomas Hallgren  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8537  
 
 
  Validator incorrectly reports result of regexp match as being forgotten   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Henrik Lindberg Thomas Hallgren  
 

  
 
 
 
 

 
 
 

 
 
 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-8519) Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG

2018-03-09 Thread Thomas Hallgren (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Hallgren assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8519  
 
 
  Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG   
 

  
 
 
 
 

 
Change By: 
 Thomas Hallgren  
 
 
Assignee: 
 Thomas Hallgren  
 

  
 
 
 
 

 
 
 

 
 
 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-8519) Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG

2018-03-09 Thread Thomas Hallgren (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Hallgren commented on  PUP-8519  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG   
 

  
 
 
 
 

 
 Merged to 5.5.x at 5c7279b.  
 

  
 
 
 
 

 
 
 

 
 
 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-8537) Validator incorrectly reports result of regexp match as being forgotten

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Henrik Lindberg  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8537  
 
 
  Validator incorrectly reports result of regexp match as being forgotten   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Henrik Lindberg  
 

  
 
 
 
 

 
 
 

 
 
 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-8537) Validator incorrectly reports result of regexp match as being forgotten

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8537  
 
 
  Validator incorrectly reports result of regexp match as being forgotten   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Fix Version/s: 
 PUP 5.5.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-8519) Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8519  
 
 
  Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Release Notes Summary: 
 If a heredoc used an empty endtag @("") it did not error the correct way and would report a Ruby NameError. Now the error correctly states that the error is raised because the end tag is empty.  
 
 
Sprint: 
 Platform Core KANBAN  
 
 
Release Notes: 
 Bug Fix  
 
 
Fix Version/s: 
 PUP 4.10.z  
 

  
 
 
 
 

 
 
 

 
 
 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" 

Jira (PUP-8519) Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG

2018-03-09 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Thomas Hallgren  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8519  
 
 
  Lexer errors with non existing Issues::HEREDOC_MISSING_ENDTAG   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Thomas Hallgren  
 

  
 
 
 
 

 
 
 

 
 
 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.