Jira (PDOC-267) Grouping of parameters

2019-05-29 Thread Ewoud Kohl van Wijngaarden (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ewoud Kohl van Wijngaarden commented on  PDOC-267  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Grouping of parameters   
 

  
 
 
 
 

 
 Yes, this is still an important use case for us. I have played around a bit, but couldn't find an easy way to implement 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.275678.1536876963000.24309.1559117040145%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9688) User resource sets password on every puppet agent run (Windows)

2019-05-29 Thread Alexandru Popa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandru Popa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9688  
 
 
  User resource sets password on every puppet agent run (Windows)   
 

  
 
 
 
 

 
 When a local group policy is configured to deny network logon's, the manifests that needs to be applied on the node are applied at every puppet run instead of only applying it once. This is issue is raised because puppet first tries to logon with credentials with the function LogonUserW using the network parameter.   Fix: The user resource will try to logon using function LogonUserW using fLOGON32_LOGON_NETWORK , if this returns false, the user resource tries to logon using fLOGON32_LOGON_INTERACTIVE to prevent applying the manifests at every agent run.  
 

  
 
 
 
 

 
Change By: 
 Alexandru Popa  
 
 
Release Notes Summary: 
 Fix: Corrective change for the password happens on the first puppet only instead of every puppet run.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 
  

Jira (FACT-1888) 'os.release' values not correct for VZ7

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1888  
 
 
  'os.release' values not correct for VZ7   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-04-03, PR - 2019-04-17, PR - 2019-05-02, PR - 2019-05-15, PR - 2019-05-29 , PR - 2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.278967.1538669961000.24397.1559121724361%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1886) Facter3 should also check for 'Virtuozzo Linux'

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1886  
 
 
  Facter3 should also check for 'Virtuozzo Linux'
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-04-17, PR - 2019-05-02, PR - 2019-05-15, PR - 2019-05-29 , PR - 2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276378.1537368012000.24387.1559121723894%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1082) pip provider should handle multiple pips/pythons

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1082  
 
 
  pip provider should handle multiple pips/pythons   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-04-17, PR - 2019-05-02, PR - 2019-05-15, PR - 2019-05-29 , PR - 2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.21416.1387220789000.24416.1559121725164%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9573) win32-service gem needs updating

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9573  
 
 
  win32-service gem needs updating   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-05-15, PR - 2019-05-29 , PR - 2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.301020.1553109081000.24428.1559121725711%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1924) Investigate if FFI works on AIX/Solaris and Solaris-sparc

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1924  
 
 
  Investigate if FFI works on AIX/Solaris and Solaris-sparc   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-05-29 , PR - 2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308706.1557915892000.24449.1559121726717%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8085) Win-2012r2 JA Puppet Acceptance showing 25 Failed Tests

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8085  
 
 
  Win-2012r2 JA Puppet Acceptance showing 25 Failed Tests   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-05-29 , PR - 2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.217992.1508850977000.24452.1559121726867%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9691) Puppet pidlock incorrectly clears lock when running under bundler

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9691  
 
 
  Puppet pidlock incorrectly clears lock when running under bundler   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-05-29 , PR - 2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307420.1556926648000.24455.1559121727007%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9697) Solaris Crontabs -> puppet resource cron only returns root account

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9697  
 
 
  Solaris Crontabs -> puppet resource cron only returns root account   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308025.155742000.24466.1559122380964%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9697) Solaris Crontabs -> puppet resource cron only returns root account

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9697  
 
 
  Solaris Crontabs -> puppet resource cron only returns root account   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308025.155742000.24483.1559122560558%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8736  
 
 
  /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.251027.1526491177000.24504.1559124240296%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8736  
 
 
  /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.251027.1526491177000.24521.1559124301080%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau commented on  PUP-8736  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs   
 

  
 
 
 
 

 
 Scope for this ticked is to implement the solution that Josh Cooper described. TODO: create a ticket to remove symlink and devicedir setting in Puppet 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.251027.1526491177000.24514.1559124300730%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1910) Mountpoint fact only shows tmpfs and physical mounts

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1910  
 
 
  Mountpoint fact only shows tmpfs and physical mounts   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299364.1552075723000.24567.1559124780318%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1910) Mountpoint fact only shows tmpfs and physical mounts

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1910  
 
 
  Mountpoint fact only shows tmpfs and physical mounts   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299364.1552075723000.24565.1559124780224%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1926  
 
 
  ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309683.1558519845000.24600.1559126280604%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1926  
 
 
  ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309683.1558519845000.24602.1559126280693%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1927) Build Facter for JRuby on redhatfips-7-x86_64

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1927  
 
 
  Build Facter for JRuby on redhatfips-7-x86_64   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.31.1558650599000.24617.1559126760625%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9722) Regression: File mode changed on every puppet run

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9722  
 
 
  Regression: File mode changed on every puppet run   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310253.1558976203000.24638.1559127360396%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9722) Regression: File mode changed on every puppet run

2019-05-29 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9722  
 
 
  Regression: File mode changed on every puppet run   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-06-12  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310253.1558976203000.24643.1559127420434%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5

2019-05-29 Thread Gabriel Nagy (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy assigned an issue to Gabriel Nagy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1926  
 
 
  ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5   
 

  
 
 
 
 

 
Change By: 
 Gabriel Nagy  
 
 
Assignee: 
 Gabriel Nagy  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309683.1558519845000.24724.1559134500446%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5

2019-05-29 Thread Gabriel Nagy (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy commented on  FACT-1926  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5   
 

  
 
 
 
 

 
 Hi, FreeBSD is community-maintained and as such we do not provide official support for it. However, I tried running this on a FreeBSD machine to reproduce your case. I added a dummy loopback interface and ran facter:  
 
 
 
 
 root@freebsd:~ # ifconfig  
 
 
 em0: flags=8843 metric 0 mtu 1500  
 
 
  options=81009b  
 
 
  ether 00:0c:29:f1:92:d1  
 
 
  inet 172.16.230.139 netmask 0xff00 broadcast 172.16.230.255   
 
 
  media: Ethernet autoselect (1000baseT )  
 
 
  status: active  
 
 
  nd6 options=29  
 
 
 lo0: flags=8049 metric 0 mtu 16384  
 
 
  options=680003  
 
 
  inet6 ::1 prefixlen 128   
 
 
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2   
 
 
  inet 127.0.0.1 netmask 0xff00   
  

Jira (PUP-9714) Add support for nested hiera interpolation

2019-05-29 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9714  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add support for nested hiera interpolation   
 

  
 
 
 
 

 
 Here is an example of how the same can be achieved with hiera 5 and a simple backend function written in Puppet Language.  
 
 
 
 
 # Do whatever is needed for a special key here that interpolates a value to form another key that is looked up.  
 
 
 # This example is hardcoded for one key only, but could easily read data from a file, support multiple keys etc.  
 
 
 #  
 
 
 function mymodule::special_key(Variant[String, Numeric] $key, Hash  $options, Puppet::LookupContext  $context) {  
 
 
   unless $key == 'hostgroup_specific_root_password' {  
 
 
 $context.not_found()  # will return from this function  
 
 
   }  
 
 
   lookup("${facts[hostgroup]}_root_password")  
 
 
 }
  
 
 
 
  Then add that function to hiera.yaml as a lookup_key kind of function, and use hiera regular interpolation in the data to get that key into the value of a hash. Using the example in the description this is what is in the data where the special value is wanted:  
 
 
 
 
 ---  
  

Jira (PUP-9714) Add support for nested hiera interpolation

2019-05-29 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9714  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add support for nested hiera interpolation   
 

  
 
 
 
 

 
 The above could be turned into a "key mapper" function. A user of the function would specify "path" to a data file, and the data file would contain the key mapping:  
 
 
 
 
 ---  
 
 
 hostgroup_specific_root_password: %{facts.hostgroup}_root_password'
  
 
 
 
  The function would read the data file given to the function in options[path], using a read_yaml function. It can then cache this result using the $context cache methods. On a lookup, it gets the data from the cache, if the key being looked up is present (e.g. 'hostgroup_specific_root_password'), it gets the value and calls $context.interpolate to interpolate it. This forms the new key, which it then uses in a call to lookup - the returned value from lookup is returned from the function. This generalized version would only be a couple of lines longer than the first example.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
  

Jira (PUP-9714) Add support for nested hiera interpolation

2019-05-29 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9714  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add support for nested hiera interpolation   
 

  
 
 
 
 

 
 I would much rather see that the requested feature is solved via use of a lookup_key kind of function than modifying hiera's interpolation to do nested interpolation.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309648.1558477577000.25078.1559144340649%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1264) Allow puppetdb plugin to set host and name independently

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1264  
 
 
  Allow puppetdb plugin to set host and name independently   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305930.1556035083000.25302.1559147041397%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1264) Allow puppetdb plugin to set host and name independently

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1264  
 
 
  Allow puppetdb plugin to set host and name independently   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Labels: 
 docs  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305930.1556035083000.25298.1559147041172%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1338) Add file::exists and file::readable functions

2019-05-29 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman assigned an issue to Cas Donoghue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1338  
 
 
  Add file::exists and file::readable functions   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Assignee: 
 Cas Donoghue  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309952.155864478.25371.1559147761362%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9720) puppet agent --fingerprint is broken

2019-05-29 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9720  
 
 
  puppet agent --fingerprint is broken   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Coremunity 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310230.1558735767000.25419.1559148600539%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9717) Puppet 6 client exits on start when it cannot connect to puppetserver

2019-05-29 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9717  
 
 
  Puppet 6 client exits on start when it cannot connect to puppetserver
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Coremunity 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309697.1558538932000.25418.1559148600491%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8563) The puppet agent should have a 'local' mode for CRL checking

2019-05-29 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8563  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The puppet agent should have a 'local' mode for CRL checking   
 

  
 
 
 
 

 
 PUP-2310 introduced the crl_refresh_interval which specifies how frequently to update the CRL. By default it behaves the same as puppet always has. It will download the CRL and never update. I think this ticket is a duplicate because if you place the CRL on the local file system, then puppet will never update the CRL. If I'm misunderstanding please reopen.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.241381.1521065231000.25442.1559148780599%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9500) Puppet assumes client cert issuer is in the ca bundle downloaded from the server

2019-05-29 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9500  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet assumes client cert issuer is in the ca bundle downloaded from the server   
 

  
 
 
 
 

 
 Agree we don't support multiple intermediate certificates currently. Given the amount of work still needed to support multiple intermediate CAs, such as SERVER-2346, I'm going to close this.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.296335.1550209791000.25472.1559149440207%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9723) Ephemeral Agents

2019-05-29 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9723  
 
 
  Ephemeral Agents   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/05/29 10:15 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 Improve the provisioning and decommissioning processes for ephemeral nodes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 


Jira (PUP-6247) Allow for certname_fact setting to be used to override default fqdn

2019-05-29 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-6247  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow for certname_fact setting to be used to override default fqdn   
 

  
 
 
 
 

 
 I moved this to a different epic so we can capture related 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.128912.1461901563000.25535.1559150281405%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9723) Ephemeral Agents

2019-05-29 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9723  
 
 
  Ephemeral Agents   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team/s: 
 Coremunity  
 
 
Epic Status: 
 To Do  
 
 
Epic Name: 
 Ephemeral Agents  
 
 
Workflow: 
 Scrum Team Engineering Epic  Workflow  
 
 
Issue Type: 
 Task Epic  
 

  
 
 
 
 

 
 
 

 
 
 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.
T

Jira (BOLT-1338) Add file::exists and file::readable functions

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1338  
 
 
  Add file::exists and file::readable functions   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Labels: 
 docs  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309952.155864478.25576.1559151060725%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1338) Add file::exists and file::readable functions

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1338  
 
 
  Add file::exists and file::readable functions   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309952.155864478.25578.1559151060821%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1348) Reconcile git commits, JIRA tickets, and versions (Bolt 1.21.0)

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1348  
 
 
  Reconcile git commits, JIRA tickets, and versions (Bolt 1.21.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/05/29 10:53 AM  
 
 
Due Date: 
2019/05/29 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-05-29) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
   

Jira (BOLT-1352) Update homebrew-puppet (Bolt 1.21.0)

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1352  
 
 
  Update homebrew-puppet (Bolt 1.21.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/05/29 10:53 AM  
 
 
Due Date: 
2019/05/29 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-05-29) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please 
 
Create a fork of the homebrew-puppet repo 
Create a new branch on that fork 
Run "rake 'brew:cask[puppet-bolt]'" 
Verify Casks/puppet-bolt.rb was updated to the correct version 
Put up a PR to homebrew-puppet and request review 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
  

Jira (BOLT-1347) Bolt 1.21.0 2019-05-29 Release

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1347  
 
 
  Bolt 1.21.0 2019-05-29 Release   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/05/29 10:53 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 Bolt 1.21.0 2019-05-29 Release  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
   

Jira (BOLT-1349) Kick off release pipeline (Bolt 1.21.0)

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1349  
 
 
  Kick off release pipeline (Bolt 1.21.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/05/29 10:53 AM  
 
 
Due Date: 
2019/05/29 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-05-29) With our shiny new automated builds pipeline, all you have to do is 
 
Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ 
Click "Build with Parameters" 
Check the PUBLIC checkbox 
Enter the version in the NEW_TAG box (x.y.z format) 
Click build! 
 And make sure the pipeline is green!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

   

Jira (BOLT-1354) Send release announcements (Bolt 1.21.0)

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1354  
 
 
  Send release announcements (Bolt 1.21.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Melissa Amos  
 
 
Created: 
 2019/05/29 10:53 AM  
 
 
Due Date: 
2019/05/29 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-05-29) Once docs have finished building (check that all links resolve appropriately) - 
 
Create an e-mail announcement with the subject "Bolt 1.21.0 now available". Include a summary of the release and links to the installation instructions and release notes. 
 
In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). 
In the Bcc: field, enter the following addresses. Send a separate message to each: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, and puppet-annou...@googlegroups.com. 
  
If this release has security implications, also send to puppet-security-annou...@googlegroups.com. 
If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 1.21.0 is now available". 
  
 

  
 
 
 
 

 

Jira (BOLT-1353) Docs for bolt release (Bolt 1.21.0)

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1353  
 
 
  Docs for bolt release (Bolt 1.21.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Melissa Amos  
 
 
Created: 
 2019/05/29 10:53 AM  
 
 
Due Date: 
2019/05/29 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-05-29) Release notes and docs changes for bolt 1.21.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (BOLT-1351) Update the release spreadsheet (Bolt 1.21.0)

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1351  
 
 
  Update the release spreadsheet (Bolt 1.21.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/05/29 10:53 AM  
 
 
Due Date: 
2019/05/29 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-05-29) Update the release google spreadsheet for Bolt 1.21.0.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (BOLT-1350) Publish release artifacts (Bolt 1.21.0)

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1350  
 
 
  Publish release artifacts (Bolt 1.21.0)   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Cas Donoghue  
 
 
Created: 
 2019/05/29 10:53 AM  
 
 
Due Date: 
2019/05/29 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Cas Donoghue  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-05-29) Run the Bolt shipping pipeline. Set REF to 1.21.0. If you encounter any issues, ping the on-call person in the #release-new-new Slack channel.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1

Jira (PDB-4379) PuppetDB CI Improvements

2019-05-29 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4379  
 
 
  PuppetDB CI Improvements   
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/05/29 11:02 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Austin Blatt  
 

  
 
 
 
 

 
 PuppetDB now auto-promotes into PE on merges to FOSS PuppetDB, but there's still more work to do w.r.t improving our CI pipelines.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 
  

Jira (PDB-4380) Add SLES 12 testing to PDB CI

2019-05-29 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4380  
 
 
  Add SLES 12 testing to PDB CI   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/05/29 11:04 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Austin Blatt  
 

  
 
 
 
 

 
 SLES 12 is a supported PE master platform, but PuppetDB acceptance tests do not pass on that platform.   sles12-64mda-64a should be added to all our LAYOUT_AXIS settings.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   

Jira (PDB-4381) Add unit test jobs to FOSS and PE puppetdb pipelines

2019-05-29 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4381  
 
 
  Add unit test jobs to FOSS and PE puppetdb pipelines   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/05/29 11:08 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Austin Blatt  
 

  
 
 
 
 

 
 With automatic promotions enabled, we should also ensure our unit tests (both in PE and FOSS and clojure/ruby) pass before promoting.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
  

Jira (PDB-4382) Create automatic mergeup job for both FOSS and PE

2019-05-29 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4382  
 
 
  Create automatic mergeup job for both FOSS and PE   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/05/29 11:10 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Austin Blatt  
 

  
 
 
 
 

 
 
 

 
 
 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 http

Jira (PDB-4383) Promote to PE when commit merged to pe-puppetdb-extensions

2019-05-29 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4383  
 
 
  Promote to PE when commit merged to pe-puppetdb-extensions   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/05/29 11:11 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Austin Blatt  
 

  
 
 
 
 

 
 
 

 
 
 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 grou

Jira (PDB-4384) Tech Debt - Use more Puppet in acceptance test setup

2019-05-29 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4384  
 
 
  Tech Debt - Use more Puppet in acceptance test setup   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/05/29 11:12 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Austin Blatt  
 

  
 
 
 
 

 
 Our acceptance tests use a lot of platform specific commands to set up packages. It would be more robust to use puppet in as many situations as possible (this may mean installing modules like puppetlabs-postgresql).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  

Jira (BOLT-1343) Bolt docs: Add info on location of Bolt directory

2019-05-29 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman assigned an issue to Lucy Wyman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1343  
 
 
  Bolt docs: Add info on location of Bolt directory
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Assignee: 
 Lucy Wyman  
 
 
Labels: 
 bolt  docs  feedback-form-docs-site  
 
 
Sprint: 
 Bolt 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310124.1558720885000.25772.1559154300741%40Atlassian.JIRA.

Jira (BOLT-1355) Bolt can't run some tasks over SSH when csh is the login shell

2019-05-29 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1355  
 
 
  Bolt can't run some tasks over SSH when csh is the login shell   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/05/29 11:52 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nick Lewis  
 

  
 
 
 
 

 
 This issue was encountered by a user in Slack. When a user has csh as their login shell, Bolt fails to run tasks that use environment variables as input, because the syntax it uses for passing environment variables is invalid in csh. Specifically, we pass them as PT_foo=bar /path/to/task, and PT_foo=bar is interpreted as the name of the command to run. We should investigate what is necessary to support running on csh.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by A

Jira (BOLT-1337) Make .filter_set called on a ResultSet return a ResultSet

2019-05-29 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1337  
 
 
  Make .filter_set called on a ResultSet return a ResultSet   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Labels: 
 docs  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309878.1558622066000.26049.1559161200383%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1325) Provide a way to send a message to the outputter

2019-05-29 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1325  
 
 
  Provide a way to send a message to the outputter   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
Summary: 
 Send Puppet logging functions Provide a way  to  send a message to  the outputter  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309516.1558393815000.26077.1559161381006%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1325) Send Puppet logging functions to the outputter

2019-05-29 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1325  
 
 
  Send Puppet logging functions to the outputter   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
Release Notes Summary: 
 This introduces a new function {{out::message()}}, which can be used to print a message to the user during a plan.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309516.1558393815000.26072.1559161380806%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1325) Send Puppet logging functions to the outputter

2019-05-29 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1325  
 
 
  Send Puppet logging functions to the outputter   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309516.1558393815000.26071.1559161380759%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1325) Provide a way to send a message to the outputter

2019-05-29 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1325  
 
 
  Provide a way to send a message to the outputter   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 

  
 
 
 
 

 
 Currently, the Puppet logging functions (notice, info, etc) call the logger directly. This means the messages are no longer sent to console below warn-level. We should add  Bolt-specific versions of these functions  a function  that  generate "log" events that are handled by  allows  the  plan to send a message to the user via the  outputter. The human outputter should print the messages to stdout ,  and  the json  outputter should ignore them,  and  the  logger  outputter  outputters  should  forward  ignore  them  to the logger .  
 

  
 
 
 
 

 
 
 

 
 
 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 t

Jira (PUP-9698) Backport PUP-8967 to 5.5.x

2019-05-29 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9698  
 
 
  Backport PUP-8967 to 5.5.x   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308037.1557423516000.26094.1559161800225%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1929) Report disks serial numbers

2019-05-29 Thread (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Romain Tartière created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1929  
 
 
  Report disks serial numbers   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/05/29 1:38 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Romain Tartière  
 

  
 
 
 
 

 
 Add a serial number attributes for the disks fact.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

   

Jira (BOLT-836) Support Hiera lookup() in plans outside of apply blocks

2019-05-29 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-836  
 
 
  Support Hiera lookup() in plans outside of apply blocks   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 h2. Feature RequestIt would be handy to support the hiera lookup() function within a plan.h2. Open QuestionWhat goes into the hierarchy for a plan? Without facter how are those values set? h2. Usecasesh4. Lookup different values to use the same plan in different environments or contextsAs a plan author i need to store data about how to execute the plan that may be environment or deployment specific. These settings would be looked up from the "perspective" of the bolt controller node. Example: may need different API keys, credentials, etc to use for API calls. Example 2: may be deploying in a different manner based on a setting in a config that is easy to switch.h4. Use hiera to lookup task parameters for different targetsAs a plan author i need to perform actions differently depending on certain facts and/or attributes of a node. These facts may be gather by the `facts` task. From these facts/attributes i then need to lookup() data to determine how the action should be run.  These facts would be looked up from the "perspective" of specific targets. Example: I'm deploying a software pacakge against a variety of hosts, some may be 32-bit some 64-bit. I need to deploy different versions of software to the 32-bit systems. I would run a 'facts' task to determine architecture, then choose which software package to copy and install. The data hierarchy would be used to uniquely specify which software package to utilize.h2. Learning from spike* currently just exposing hiera allows backends to work without interpolation as long as all interpolation is based on $facts and $trusted. The fact that those are set during plan execution feels wrong and may be a bug.* We probably need the ability for users to specify a separate hiearchy for the plan level so we don't limit interpolation options.* There is value in exposing backends so that hiera-eyaml can be used but this problem may be solved by supporting eyaml in inventory. h1 Questions for commentors* What levels of heirarchy would you use at the plan level?* Would there be any fact like interpolations in the hierarchy? What values would be used.* Do you expect values from plan level data to be automatically set anywhere with data bindings like classes in manifests.  
 

  
 
 
 
 

 
 
 

 

Jira (BOLT-1264) Allow puppetdb plugin to set host and name independently

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1264  
 
 
  Allow puppetdb plugin to set host and name independently   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Release Notes Summary: 
 The PuppetDB plugin can no be used to lookup configuration values for the `name`, `uri`, and `config` inventory options for each target.  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305930.1556035083000.26298.1559166060699%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1337) Make .filter_set called on a ResultSet return a ResultSet

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1337  
 
 
  Make .filter_set called on a ResultSet return a ResultSet   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309878.1558622066000.26304.1559166180607%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1337) Make .filter_set called on a ResultSet return a ResultSet

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1337  
 
 
  Make .filter_set called on a ResultSet return a ResultSet   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Release Notes Summary: 
 A {{filter_set}} function has been added to the {{ResultSet}} data type which allows filtering a {{ResultSet}} with a lambda to return a filtered {{ResultSet}}.   
 
 
Release Notes: 
 Enhancement  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309878.1558622066000.26311.1559166420575%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1264) Allow puppetdb plugin to set host and name independently

2019-05-29 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1264  
 
 
  Allow puppetdb plugin to set host and name independently   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Release Notes Summary: 
 The PuppetDB plugin can  no  now  be used to lookup configuration values  from PuppetDB facts  for the `name`, `uri`, and `config` inventory options for each target.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305930.1556035083000.26324.155910157%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1337) Make .filter_set called on a ResultSet return a ResultSet

2019-05-29 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1337  
 
 
  Make .filter_set called on a ResultSet return a ResultSet   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Release Notes Summary: 
 A {{filter_set}} function has been added to the {{ResultSet}} data type which  allows filtering  filters  a {{ResultSet}} with a lambda to return a  filtered  {{ResultSet}}  object .   
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309878.1558622066000.26331.1559166720753%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1297) Bolt should raise a nice error if the private key file doesn't exist

2019-05-29 Thread Melissa Amos (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Amos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1297  
 
 
  Bolt should raise a nice error if the private key file doesn't exist   
 

  
 
 
 
 

 
Change By: 
 Melissa Amos  
 
 
Labels: 
 docs_reviewed  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307991.1557409042000.26329.1559166720656%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1325) Provide a way to send a message to the outputter

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1325  
 
 
  Provide a way to send a message to the outputter   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309516.1558393815000.26531.1559169420969%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1325) Provide a way to send a message to the outputter

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1325  
 
 
  Provide a way to send a message to the outputter   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Labels: 
 docs  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309516.1558393815000.26526.1559169420734%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1338) Add file::exists and file::readable functions

2019-05-29 Thread Melissa Amos (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Amos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1338  
 
 
  Add file::exists and file::readable functions   
 

  
 
 
 
 

 
Change By: 
 Melissa Amos  
 
 
Labels: 
 docs  docs_reviewed  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309952.155864478.26543.1559169600673%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1337) Make .filter_set called on a ResultSet return a ResultSet

2019-05-29 Thread Melissa Amos (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Amos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1337  
 
 
  Make .filter_set called on a ResultSet return a ResultSet   
 

  
 
 
 
 

 
Change By: 
 Melissa Amos  
 
 
Labels: 
 docs  docs_reviewed  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309878.1558622066000.26548.1559169720426%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1158) Publish bash helper library

2019-05-29 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue commented on  BOLT-1158  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Publish bash helper library   
 

  
 
 
 
 

 
 A potential starting point has been included by Adrian Parreiras Horta in the package and service modules. https://github.com/puppetlabs/puppetlabs-service/pull/96/commits/1d06ba603d10afe7b344c01a14f6dc2efdc62a96  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.298394.1551810745000.26606.1559170440262%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1337) Make .filter_set called on a ResultSet return a ResultSet

2019-05-29 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman commented on  BOLT-1337  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make .filter_set called on a ResultSet return a ResultSet   
 

  
 
 
 
 

 
 Melissa Amos The first looks good! The second looks like it doesn't have filter_set on it, but might also just be linked wrong?  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309878.1558622066000.26621.1559170560464%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1356) Make example strings documentation for a plan

2019-05-29 Thread Jesse Scott (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Scott created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1356  
 
 
  Make example strings documentation for a plan   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/05/29 5:21 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Jesse Scott  
 

  
 
 
 
 

 
 
 

 
 
 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:/

Jira (BOLT-1356) Make example strings documentation for a plan

2019-05-29 Thread Jesse Scott (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Scott updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1356  
 
 
  Make example strings documentation for a plan   
 

  
 
 
 
 

 
Change By: 
 Jesse Scott  
 
 
Reporter: 
 Jesse Scott 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310714.1559175692000.26749.1559175720999%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.