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

2019-03-22 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3122  
 
 
  It's time we wrote a more usable no cert found warning!   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Coremunity Hopper 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-3122) It's time we wrote a more usable no cert found warning!

2019-03-22 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3122  
 
 
  It's time we wrote a more usable no cert found warning!   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 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-9574) allow_duplicate_certs description is misleading

2019-03-22 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9574  
 
 
  allow_duplicate_certs description is misleading   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Coremunity Hopper 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-9574) allow_duplicate_certs description is misleading

2019-03-22 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9574  
 
 
  allow_duplicate_certs description is misleading   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 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-9579) device application is broken in 6.4

2019-03-22 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9579  
 
 
  device application is broken in 6.4   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 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-9472) Use OpenSSL::X509::Name#to_utf8

2019-03-22 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9472  
 
 
  Use OpenSSL::X509::Name#to_utf8   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 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-9472) Use OpenSSL::X509::Name#to_utf8

2019-03-22 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9472  
 
 
  Use OpenSSL::X509::Name#to_utf8   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Coremunity Hopper 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-9579) device application is broken in 6.4

2019-03-22 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9579  
 
 
  device application is broken in 6.4   
 

  
 
 
 
 

 
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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9579) device application is broken in 6.4

2019-03-22 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9579  
 
 
  device application is broken in 6.4   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.4.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-9579) device application is broken in 6.4

2019-03-22 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9579  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: device application is broken in 6.4   
 

  
 
 
 
 

 
 The device application needs to ensure it has a client cert for the device before trying to make network connection on behalf of the device.  
 

  
 
 
 
 

 
 
 

 
 
 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-9579) device application is broken in 6.4

2019-03-22 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9579  
 
 
  device application is broken in 6.4   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/03/22 4:20 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 The device application doesn't work if it attempts to download a catalog for multiple nodes in the same run. The result is similar to FM-7876, but the cause is different.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
   

Jira (BOLT-1193) Analytics for simple plan usage

2019-03-22 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1193  
 
 
  Analytics for simple plan usage   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1193) Analytics for simple plan usage

2019-03-22 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis assigned an issue to Nick Lewis  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1193  
 
 
  Analytics for simple plan usage   
 

  
 
 
 
 

 
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 (BOLT-1190) Fix scope for run_plan

2019-03-22 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1190  
 
 
  Fix scope for run_plan   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1200) Localhost supplies the puppet-agent feature

2019-03-22 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1200  
 
 
  Localhost supplies the puppet-agent feature   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/03/22 2:20 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Alex Dreyer  
 

  
 
 
 
 

 
 Since the localhost target runs ruby tasks in bolt's ruby and the puppet gem is installed we should probably add the puppet-agent feature to that target. caveat: tasks that shell out to /opt/puppetlabs/bin/puppet won't work  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

   

Jira (BOLT-1190) Fix scope for run_plan

2019-03-22 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1190  
 
 
  Fix scope for run_plan   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
Release Notes Summary: 
 Variables defined in scope in a plan will no longer be visible to sub-plans called via {{run_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.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1190) Fix scope for run_plan

2019-03-22 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1190  
 
 
  Fix scope for run_plan   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
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 (BOLT-1190) Fix scope for run_plan

2019-03-22 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis assigned an issue to Nick Lewis  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1190  
 
 
  Fix scope for run_plan   
 

  
 
 
 
 

 
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-9534) Prepare JIRA for release (Puppet Platform 6.0.7)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9534  
 
 
  Prepare JIRA for release (Puppet Platform 6.0.7)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Prepare JIRA for release (Puppet Platform 6.0. 6 7 )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9537) Prepare release announcement (Puppet Platform 6.0.7)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9537  
 
 
  Prepare release announcement (Puppet Platform 6.0.7)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Prepare release announcement (Puppet Platform 6.0. 6 7 )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9534) Prepare JIRA for release (Puppet Platform 6.0.7)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9534  
 
 
  Prepare JIRA for release (Puppet Platform 6.0.7)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-03-26)1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release.2) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA.3) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it.4) Update the “master” filters for Puppet Platform 6.0. 6 7  and puppet-agent 6.0. 6 7  to reference the “Fixed in” filters created above.5) Update the community feedback filter for Puppet Platform X.y to reference the “Introduced in” filter created above.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by 

Jira (PUP-9536) Prepare documentation updates and release notes (Puppet Platform 6.0.7)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9536  
 
 
  Prepare documentation updates and release notes (Puppet Platform 6.0.7)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Prepare documentation updates and release notes (Puppet Platform 6.0. 6 7 )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9540) Send release announcement (Puppet Platform 6.0.7)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9540  
 
 
  Send release announcement (Puppet Platform 6.0.7)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Send release announcement (Puppet Platform 6.0. 6 7 )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9539) Publish documentation and updates and release notes (Puppet Platform 6.0.7)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9539  
 
 
  Publish documentation and updates and release notes (Puppet Platform 6.0.7)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Publish documentation and updates and release notes (Puppet Platform 6.0. 6 7 )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9535) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.7)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9535  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.7)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0. 6 7 )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9541) Update Confluence and JIRA based on release (Puppet Platform 6.0.7)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9541  
 
 
  Update Confluence and JIRA based on release (Puppet Platform 6.0.7)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Update Confluence and JIRA based on release (Puppet Platform 6.0. 6 7 )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9542) Communicate scope and timeline of next release (Puppet Platform 6.0.7)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9542  
 
 
  Communicate scope and timeline of next release (Puppet Platform 6.0.7)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Communicate scope and timeline of next release (Puppet Platform 6.0. 6 7 )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9540) Send release announcement (Puppet Platform 6.0.7)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9540  
 
 
  Send release announcement (Puppet Platform 6.0.7)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-03-26)Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account -* Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send.* If this release has security implications, also send to puppet-security-annou...@googlegroups.com.* Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.0. 6 7  is now available".   
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-9538) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.0.7)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9538  
 
 
  Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.0.7)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.0. 6 7 )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9533) Puppet Platform 6.0.7 Release - 2019-03-26

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9533  
 
 
  Puppet Platform 6.0.7 Release - 2019-03-26   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 

  
 
 
 
 

 
 Puppet Platform 6.0. 6 7  Release - 2019-03-26   
 

  
 
 
 
 

 
 
 

 
 
 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-9533) Puppet Platform 6.0.7 Release - 2019-03-26

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9533  
 
 
  Puppet Platform 6.0.7 Release - 2019-03-26   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Puppet Platform 6.0. 6 7  Release - 2019-03-26   
 

  
 
 
 
 

 
 
 

 
 
 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-9533) Puppet Platform 6.0.7 Release - 2019-03-26

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9533  
 
 
  Puppet Platform 6.0.7 Release - 2019-03-26   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Epic Name: 
 Puppet Platform 6.0. 6 7  Release - 2019-03-26   
 

  
 
 
 
 

 
 
 

 
 
 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-9524) Prepare JIRA for release (Puppet Platform 5.5.12)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9524  
 
 
  Prepare JIRA for release (Puppet Platform 5.5.12)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-03-26)1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release.2) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA.3) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it.4) Update the “master” filters for Puppet Platform 5.5. 11 12  and puppet-agent 5.5. 11 12  to reference the “Fixed in” filters created above.5) Update the community feedback filter for Puppet Platform X.y to reference the “Introduced in” filter created above.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was 

Jira (PUP-9524) Prepare JIRA for release (Puppet Platform 5.5.12)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9524  
 
 
  Prepare JIRA for release (Puppet Platform 5.5.12)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Prepare JIRA for release (Puppet Platform 5.5. 11 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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9529) Publish documentation and updates and release notes (Puppet Platform 5.5.12)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9529  
 
 
  Publish documentation and updates and release notes (Puppet Platform 5.5.12)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Publish documentation and updates and release notes (Puppet Platform 5.5. 11 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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9527) Prepare release announcement (Puppet Platform 5.5.12)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9527  
 
 
  Prepare release announcement (Puppet Platform 5.5.12)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Prepare release announcement (Puppet Platform 5.5. 11 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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9528) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.12)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9528  
 
 
  Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.12)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5. 11 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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9525) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.12)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9525  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.12)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5. 11 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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9526) Prepare documentation updates and release notes (Puppet Platform 5.5.12)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9526  
 
 
  Prepare documentation updates and release notes (Puppet Platform 5.5.12)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Prepare documentation updates and release notes (Puppet Platform 5.5. 11 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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9530) Send release announcement (Puppet Platform 5.5.12)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9530  
 
 
  Send release announcement (Puppet Platform 5.5.12)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Send release announcement (Puppet Platform 5.5. 11 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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9531) Update Confluence and JIRA based on release (Puppet Platform 5.5.12)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9531  
 
 
  Update Confluence and JIRA based on release (Puppet Platform 5.5.12)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Update Confluence and JIRA based on release (Puppet Platform 5.5. 11 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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9530) Send release announcement (Puppet Platform 5.5.12)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9530  
 
 
  Send release announcement (Puppet Platform 5.5.12)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-03-26)Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account -* Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send.* If this release has security implications, also send to puppet-security-annou...@googlegroups.com.* Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 5.5. 11 12  is now available".   
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-9532) Communicate scope and timeline of next release (Puppet Platform 5.5.12)

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9532  
 
 
  Communicate scope and timeline of next release (Puppet Platform 5.5.12)   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Communicate scope and timeline of next release (Puppet Platform 5.5. 11 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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9523) Puppet Platform 5.5.12 Release - 2019-03-26

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9523  
 
 
  Puppet Platform 5.5.12 Release - 2019-03-26   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 

  
 
 
 
 

 
 Puppet Platform 5.5. 11 12  Release - 2019-03-26   
 

  
 
 
 
 

 
 
 

 
 
 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-9523) Puppet Platform 5.5.12 Release - 2019-03-26

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9523  
 
 
  Puppet Platform 5.5.12 Release - 2019-03-26   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Epic Name: 
 Puppet Platform 5.5. 11 12  Release - 2019-03-26   
 

  
 
 
 
 

 
 
 

 
 
 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-9523) Puppet Platform 5.5.12 Release - 2019-03-26

2019-03-22 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9523  
 
 
  Puppet Platform 5.5.12 Release - 2019-03-26   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Summary: 
 Puppet Platform 5.5. 11 12  Release - 2019-03-26   
 

  
 
 
 
 

 
 
 

 
 
 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-1190) Fix scope for run_plan

2019-03-22 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1190  
 
 
  Fix scope for run_plan   
 

  
 
 
 
 

 
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-1199) Fact to check whether a catalog is being compiled by bolt.

2019-03-22 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1199  
 
 
  Fact to check whether a catalog is being compiled by bolt.   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/03/22 11:05 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Alex Dreyer  
 

  
 
 
 
 

 
 To update existing modules in a non-breaking fashion to work with bolt it's sometimes useful to know whether they are being used from a bolt catalog or not. Example: The selinux module uses the puppet_vardir fact to decide where to build selinux modules. This is a weird place for them and definitely will not work with bolt since that vardir is temporary and isn't even consistent between fact collection and catalog execution. Questions what is this fact called?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
  

Jira (PUP-9577) Large numbers of facts cause slow performance

2019-03-22 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen commented on  PUP-9577  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Large numbers of facts cause slow performance   
 

  
 
 
 
 

 
 In addition to improvements in the compiler, we should also take a look at implementing FACT-1575 — which would allow facts to be filtered on the agent.  
 

  
 
 
 
 

 
 
 

 
 
 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-1017) Inventory should warn when unexepected keys are at the top of a node or group object

2019-03-22 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1017  
 
 
  Inventory should warn when unexepected keys are at the top of a node or group object   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Release Notes Summary: 
 Helpful warning message is logged when invalid {{group}} or {{node}} configuration keys are detected in the {{inventoryfile}}.  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1017) Inventory should warn when unexepected keys are at the top of a node or group object

2019-03-22 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1017  
 
 
  Inventory should warn when unexepected keys are at the top of a node or group object   
 

  
 
 
 
 

 
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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9437) Make it easier to set Puppets current locale

2019-03-22 Thread Thomas Honey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Honey commented on  PUP-9437  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Make it easier to set Puppets current locale   
 

  
 
 
 
 

 
 https://github.com/puppetlabs/beaker-i18n_helper/blob/master/lib/beaker/i18n_helper.rb https://github.com/puppetlabs/puppetlabs-motd/blob/master/spec/acceptance/locales_spec.rb  
 

  
 
 
 
 

 
 
 

 
 
 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-953) Add file_upload support to BoltSpec

2019-03-22 Thread Melissa Amos (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Amos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-953  
 
 
  Add file_upload support to BoltSpec   
 

  
 
 
 
 

 
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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9578) Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`

2019-03-22 Thread Reid Vandewiele (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Reid Vandewiele updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9578  
 
 
  Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`   
 

  
 
 
 
 

 
Change By: 
 Reid Vandewiele  
 

  
 
 
 
 

 
 Right now users need to manually indicate to the syntax validation command whether or not they will be passing in manifest data that uses plan features.  {code}  puppet parser validate{code}  {code}  puppet parser validate --tasks{code}  *Assertion:*  the only  what  validation  differences between these two commands  is appropriate  can be  automatically  detected  automatically  and set  appropriately  based on  being in,  the first encounter of manifest-specific  or  not being in, a {{ plan }} block -specific constructs .Given the above assertion, we should remove the user burden of needing to indicate to {{puppet parser validate}} when plan code is input  vs .  Rather  when manifest code is input. Optionally ,  we can allow users to pass {{--tasks}} or a new flag such as {{--manifests}} to explicitly indicate purpose, but when run without flags  the  parser/validator  command  should  Do The Right Thing™ automatically  be able to validate either kind of Puppet DSL content .Eliminate the  need  _need_  to pass {{--tasks}}  in any circumstance  to validate plans  by  auto- detecting  the first  plan  blocks - or manifest-specific constructs  and  validating inside them appropriately  selecting a validation mode accordingly .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (PUP-9578) Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`

2019-03-22 Thread Reid Vandewiele (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Reid Vandewiele updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9578  
 
 
  Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`   
 

  
 
 
 
 

 
Change By: 
 Reid Vandewiele  
 

  
 
 
 
 

 
 Right now users need to manually indicate to the syntax validation command whether or not they will be passing in manifest data that uses plan features.{code}puppet parser validate{code}{code}puppet parser validate --tasks{code}*Assertion:* what validation is appropriate can be detected automatically and set based on the first encounter of manifest-specific or plan-specific constructs.Given the above assertion, we should remove the user burden of needing to indicate to {{puppet parser validate}} when plan code is input vs. when manifest code is input. Optionally, we can allow users to pass {{ \ - \ -tasks}} or a new flag such as {{ \ - \ -manifests}} to explicitly indicate purpose, but when run without flags the command should be able to validate either kind of Puppet DSL content.Eliminate the _need_ to pass {{ \ - \ -tasks}} to validate plans by detecting the first plan- or manifest-specific constructs and selecting a validation mode accordingly.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

Jira (BOLT-1119) Improve Bolt startup time on Windows for bolt --help

2019-03-22 Thread Ethan Brown (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Brown commented on  BOLT-1119  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve Bolt startup time on Windows for bolt --help   
 

  
 
 
 
 

 
 My tests have been confined to a single host / scenario, so I'm not entirely comfortable with advertising "% faster" or absolute times improvements like "3 seconds faster" as that can be wildly variable based on machine. The focus of this work has been primarily on improving the path to something like bolt --help for now, but will expand out to encompass other common operations in later tickets / efforts. So for now, it's been about not loading code that we'll never need OR lazy-loading code when we need it (which will make small improvements across all operating systems - regardless of whether or not we're just asking for bolt --help or doing real work).  
 

  
 
 
 
 

 
 
 

 
 
 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-1132) Environment variables do not propagate to actions run on localhost.

2019-03-22 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer assigned an issue to Kevin Reeuwijk  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1132  
 
 
  Environment variables do not propagate to actions run on localhost.   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Assignee: 
 Alex Dreyer Kevin Reeuwijk  
 

  
 
 
 
 

 
 
 

 
 
 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-1186) Improve Bolt startup time on Windows redux

2019-03-22 Thread Ethan Brown (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1186  
 
 
  Improve Bolt startup time on Windows redux   
 

  
 
 
 
 

 
Change By: 
 Ethan Brown  
 
 
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-1052) Support run-as for shell localhost transport.

2019-03-22 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1052  
 
 
  Support run-as for shell localhost transport.   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9577) Large numbers of facts cause slow performance

2019-03-22 Thread Brian Rak (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Rak commented on  PUP-9577  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Large numbers of facts cause slow performance   
 

  
 
 
 
 

 
 So test3.patch did not provide sufficient resolution for this issue (despite looking good in the benchmarks).  I applied another patch to our masters after this, which filtered out all the facts we didn't care about right at load time.  This reduced the number of facts per agent from ~6400 to ~1200, and had significant impacts on our master loads (to the degree where I could probably eliminate 6 out of 8 masters and still be fine). This is a snapshot of the data coming out of puppet server: https://snapshot.raintank.io/dashboard/snapshot/OOdS1Og23IHvHG73kC2FTcWIMGDVX4mp 
 
I applied the fact reducing patch to puppetmaster2 at 11:10, and puppetmaster4 at ~11:15 (you can see the request duration drop then).  The # of active requests to these stayed high because they were picking up a significant portion of the load (our load balancer is configured to pick the one with the least connections), note the total requests count graph around then. 
I patched the rest of the masters around 11:20. The performance increase was immediate, and everything is behaving normally now.  
 I've attached the CPU usage graphs from one of our masters, which shows a very significant drop as well. I should also note that as part of this I made our load balancer cache the results of requests for file_metadatas, static_file_content, file_metadata, and file_content.  This did not have any significant effect on the puppet master loads. I have attached my fact cleanup patch with the note that this is specific to our environment, and I have minimal ruby skills   It might be helpful if someone else comes across this issue though.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

   

Jira (PUP-9577) Large numbers of facts cause slow performance

2019-03-22 Thread Brian Rak (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Rak updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9577  
 
 
  Large numbers of facts cause slow performance   
 

  
 
 
 
 

 
Change By: 
 Brian Rak  
 
 
Attachment: 
 cpu_usage.png  
 

  
 
 
 
 

 
 
 

 
 
 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-1052) Support run-as for shell localhost transport.

2019-03-22 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1052  
 
 
  Support run-as for shell localhost transport.   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Release Notes Summary: 
 Adds support for `run-as`, `sudo-password`, and `run-as-command` options when running over the local transport on non-Windows nodes. These options escalate the system user (which ran `bolt`) to the provided user, and behave just like the same options using the SSH transport. `_run_as` can also be configured for individual plan function calls for the local transport.  
 
 
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 

Jira (PUP-9043) file resource - mtime checksum does not seem to work

2019-03-22 Thread Jeff Sparrow (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Sparrow commented on  PUP-9043  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: file resource - mtime checksum does not seem to work   
 

  
 
 
 
 

 
 Any idea when or what puppet/ruby build this will be fixed in? It continues to be an issues with multiple vendors.  
 

  
 
 
 
 

 
 
 

 
 
 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-9578) Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`

2019-03-22 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9578  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove distinction between `puppet parser validate` and `puppet parser validate --tasks`   
 

  
 
 
 
 

 
 Let's see... I can imagine that we validate and accept everything from both modes and then we check if there is a mix of constructs and if so fail While it does not capture the error of "you cannot do this when..." it does at least catch constructs that will never work. At runtime we must validate for one or the other - like now. This means that in any case, there needs to be a different validator for the parser validate case - it can probably be feature switched such that every encounter of a catalog related construct sets a flag and it remembers the first one it got - it does the same for task related constructs - when one trips the other it is an error and it can be reported as "cannot mix this... with that..." and get both locations. So this would need to be a different mode - it could be the default for parser validate, and it could have options for taks and catalog compilation to test specifically for one or the other mode.  
 

  
 
 
 
 

 
 
 

 
 
 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.