Jira (FACT-1500) Message catalog generation fails on Windows

2016-09-14 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1500 
 
 
 
  Message catalog generation fails on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 i18n 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-5831) Add a Binary type and runtime object

2016-09-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5831 
 
 
 
  Add a Binary type and runtime object  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6703) Minor improvement to agent failover test (originally PUP-6383)

2016-09-14 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6703 
 
 
 
  Minor improvement to agent failover test (originally PUP-6383)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Assignee:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6703) Minor improvement to agent failover test (originally PUP-6383)

2016-09-14 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-6703 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Minor improvement to agent failover test (originally PUP-6383)  
 
 
 
 
 
 
 
 
 
 
Branan Riley thoughts?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2403) Should include parser function to generate a "stack trace"

2016-09-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-2403 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Should include parser function to generate a "stack trace"  
 
 
 
 
 
 
 
 
 
 
Since Puppet 4.6.0, the 4.x function API has a mechanism known as PuppetStack that contains the call frames with references to the .pp file and line numbers of calls. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2982) Create shorter command names for the stockpile metadata

2016-09-14 Thread Dan Lidral-Porter (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Lidral-Porter assigned an issue to Dan Lidral-Porter 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2982 
 
 
 
  Create shorter command names for the stockpile metadata  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dan Lidral-Porter 
 
 
 

Assignee:
 
 Dan Lidral-Porter 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6699) Leading zero with cron resource is not handled as expected.

2016-09-14 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6699 
 
 
 
  Leading zero with cron resource is not handled as expected.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6704) Handle return type added in PUP-5623

2016-09-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6704 
 
 
 
  Handle return type added in PUP-5623  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/09/14 4:46 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
In 

PUP-5623
 the ability to declare the return type of functions (and lambdas) was added. Earlier the return type could otherwise only be in documentation using the yard @return tag. 
It would be great if the documentation picks up the return type if it is stated to avoid having to maintain it in more than one place. 
The default return type is Any. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

Jira (PUP-6703) Minor improvement to agent failover test (originally PUP-6383)

2016-09-14 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza assigned an issue to Moses Mendoza 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6703 
 
 
 
  Minor improvement to agent failover test (originally PUP-6383)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Assignee:
 
 Moses Mendoza 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6703) Minor improvement to agent failover test (originally PUP-6383)

2016-09-14 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6703 
 
 
 
  Minor improvement to agent failover test (originally PUP-6383)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/09/14 4:11 PM 
 
 
 

Labels:
 

 ci 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Moses Mendoza 
 
 
 
 
 
 
 
 
 
 
On 9/14 we had a failed cell (spurious failure) in the matrix run for test acceptance/tests/reports/failover_master.rb due to a timeout sending the report to the master for the test 'master_field should not appear when no master could be contacted'.  
That test currently uses two nonexistent servers in a server list and specifies a timeout of 3 seconds, and checks that the master does not show up in the report for the value `master_used`.  
This ticket is to update that test to increase the timeout, but only check with one nonexistent master as a way to diminish the impact on overall test time of increasing the timeout. The fact that two masters are specified isn't actually intrinsic to the test.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
  

Jira (PDB-3055) Externalize user facing strings in the trapperkeeper repo

2016-09-14 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3055 
 
 
 
  Externalize user facing strings in the trapperkeeper repo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Team:
 
 Engineering "Pool" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-3055) Externalize user facing strings in the trapperkeeper repo

2016-09-14 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3055 
 
 
 
  Externalize user facing strings in the trapperkeeper repo  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/09/14 3:36 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Karen Van der Veer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-3054) Externalize user facing strings in the tk-webserver-jetty9 repo

2016-09-14 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3054 
 
 
 
  Externalize user facing strings in the tk-webserver-jetty9 repo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Team:
 
 Engineering "Pool" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-3054) Externalize user facing strings in the tk-webserver-jetty9 repo

2016-09-14 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3054 
 
 
 
  Externalize user facing strings in the tk-webserver-jetty9 repo  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/09/14 3:27 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Karen Van der Veer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-3053) Create Index on certname latest_report_id

2016-09-14 Thread Nick Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3053 
 
 
 
  Create Index on certname latest_report_id  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Walker 
 
 
 

Labels:
 
 tcse 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-3053) Create Index on certname latest_report_id

2016-09-14 Thread Nick Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3053 
 
 
 
  Create Index on certname latest_report_id  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 PDB 4.1.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 PuppetDB 
 
 
 

Created:
 

 2016/09/14 3:05 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Nick Walker 
 
 
 
 
 
 
 
 
 
 
The Problem 
Event Inspector is incredibly slow with large amounts of nodes.  
The Solution 
 
 
 
 
 
 
CREATE UNIQUE INDEX certnames_latest_report_id ON certnames(latest_report_id);
 
 
 
 
 
 
 
Query Plans  
Before Index ( 5+ mins ) :  

Jira (FACT-718) Allow for disabling certain facts within Facter

2016-09-14 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-718 
 
 
 
  Allow for disabling certain facts within Facter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 Glenn Sarti qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-718) Allow for disabling certain facts within Facter

2016-09-14 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  FACT-718 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow for disabling certain facts within Facter  
 
 
 
 
 
 
 
 
 
 
Build completed with success https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/facter/job/platform_facter_pkg-van-promote_master/84/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6699) Leading zero with cron resource is not handled as expected.

2016-09-14 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6699 
 
 
 
  Leading zero with cron resource is not handled as expected.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 APS Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1506) sp_serial_number is empty on macOS Sierra (10.12)

2016-09-14 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1506 
 
 
 
  sp_serial_number is empty on macOS Sierra (10.12)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 APS Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1356) External facts should be able to return structured data

2016-09-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1356 
 
 
 
  External facts should be able to return structured data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-77) Create an easy way to modify the rake task to include/exclude certain files/folders.

2016-09-14 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene commented on  PDOC-77 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create an easy way to modify the rake task to include/exclude certain files/folders.  
 
 
 
 
 
 
 
 
 
 
With the new generate task, you should be able to do this: 
 
 
 
 
 
 
rake strings:generate\["site/**/*.pp modules/custom/**/*.rb modules/custom/**/*.pp"]
 
 
 
 
 
 
 
That would filter to only parse Puppet source under site/, and Ruby and Puppet source under modules/custom/. No need to write a custom task or any Ruby code. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-73) handle type aliases in 4.x ruby functions (introduced in PUP-5903)

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PDOC-73 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: handle type aliases in 4.x ruby functions (introduced in PUP-5903)  
 
 
 
 
 
 
 
 
 
 
This may be addressed by Peter's rewrite. I will investigate.. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-80) Installation overwrites facter in PE 3.8.3

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-80 
 
 
 
  Installation overwrites facter in PE 3.8.3  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Team:
 
 Puppet Developer Support 
 
 
 

Sprint:
 
 PDS 2016-10-05 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-80) Installation overwrites facter in PE 3.8.3

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PDOC-80 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Installation overwrites facter in PE 3.8.3  
 
 
 
 
 
 
 
 
 
 
I ran into this in the FOSS world as well. It can be reproduced just by installing puppet-agent and then following the README instructions to install the gem with puppet. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-89) Strings should exit 1 when an error occurs

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-89 
 
 
 
  Strings should exit 1 when an error occurs  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Summary:
 
 Exit Strings should exit  1 when an error occurs 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-58) strings server throws unhandled exception

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-58 
 
 
 
  strings server throws unhandled exception  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Assignee:
 
 Hailee Kenney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-77) Create an easy way to modify the rake task to include/exclude certain files/folders.

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PDOC-77 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create an easy way to modify the rake task to include/exclude certain files/folders.  
 
 
 
 
 
 
 
 
 
 
I believe Peter Huene's rewrite addresses this. Once we get that merged in I'll verify it works and we can close this out. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-2791) Test stockpile/store's error cases more thoroughly.

2016-09-14 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning assigned an issue to Rob Browning 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2791 
 
 
 
  Test stockpile/store's error cases more thoroughly.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Assignee:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-718) Allow for disabling certain facts within Facter

2016-09-14 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  FACT-718 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow for disabling certain facts within Facter  
 
 
 
 
 
 
 
 
 
 
Build started at; https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/facter/job/platform_facter_init-van-component_master/103/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-83) Define a proper JSON schema for strings

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-83 
 
 
 
  Define a proper JSON schema for strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Sprint:
 
 PDS 2016-10-05 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-60) Strings skips docs for the log message functions

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-60 
 
 
 
  Strings skips docs for the log message functions  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Sprint:
 
 PDS 2016-10-05 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-718) Allow for disabling certain facts within Facter

2016-09-14 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  FACT-718 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow for disabling certain facts within Facter  
 
 
 
 
 
 
 
 
 
 
FACT-1507 has been raised to address acceptance tests. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-85) Handle the case of 4x functions and 3x stubs

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-85 
 
 
 
  Handle the case of 4x functions and 3x stubs  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Sprint:
 
 PDS 2016-10-05 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-718) Allow for disabling certain facts within Facter

2016-09-14 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  FACT-718 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow for disabling certain facts within Facter  
 
 
 
 
 
 
 
 
 
 
Merged into master at; https://github.com/puppetlabs/facter/commit/72e0260341a4ca52831d6520cd5f123d441e24ea 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1507) acceptance: test fact blocklist in config file

2016-09-14 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1507 
 
 
 
  acceptance: test fact blocklist in config file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Acceptance Criteria:
 
 * Acceptance test to read a facter config file in default location* Acceptance test to read a facter config file in custom location* Acceptance test to block fileystem tests on linux based platform and confirm facts are not output* Acceptance test to block all blokckable tests and confirm that any facts that are required are still present (Checks that facts deemed critical still exist) 
 
 
 

Sprint:
 
 APS Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1507) acceptance: test fact blocklist in config file

2016-09-14 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1507 
 
 
 
  acceptance: test fact blocklist in config file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Acceptance Criteria:
 
 * Acceptance test to read a facter config file in default location* Acceptance test to read a facter config file in custom location* Acceptance test to block fileystem tests on linux based platform and confirm facts are not output* Acceptance test to block all  blokckable  blockable  tests and confirm that any facts that are required are still present (Checks that facts deemed critical still exist) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-348) Facter should provide a convenient way to cache values

2016-09-14 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer assigned an issue to Maggie Dreyer 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-348 
 
 
 
  Facter should provide a convenient way to cache values  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Assignee:
 
 Maggie Dreyer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1507) acceptance: test fact blocklist in config file

2016-09-14 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1507 
 
 
 
  acceptance: test fact blocklist in config file  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/09/14 1:22 PM 
 
 
 

Fix Versions:
 

 FACT 3.5.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Maggie Dreyer 
 
 
 
 
 
 
 
 
 
 
We need some acceptance tests that verify that the blocklist in the config file is respected both when running Facter from the command line and when using it as a Ruby library (e.g. in Puppet). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
   

Jira (PUP-6701) PE Everett fails to install: Unknown function: 'puppetdb_query'

2016-09-14 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6701 
 
 
 
  PE Everett fails to install: Unknown function: 'puppetdb_query'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Sprint:
 
 APS PDS  2016-09-21  Redux 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-95) Strings doesn't handle multiple `defaultfor`s in providers correctly

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-95 
 
 
 
  Strings doesn't handle multiple `defaultfor`s in providers correctly  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PDOC 0.4.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/09/14 12:56 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 William Hopper 
 
 
 
 
 
 
 
 
 
 
Note: this also affects Peter's rewrite. 
Example: the systemd service provider: 
 
 
 
 
 
 
  defaultfor :osfamily => [:archlinux]│ 
 
 
 
 
  defaultfor :osfamily => :redhat, :operatingsystemmajrelease => "7"  │ 
 
 
 
   

Jira (PDOC-88) Create a test plan for ensuring strings support going forward

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-88 
 
 
 
  Create a test plan for ensuring strings support going forward  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Summary:
 
 Create a  test  plan for ensuring strings support going forward 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-85) Handle the case of 4x functions and 3x stubs

2016-09-14 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-85 
 
 
 
  Handle the case of 4x functions and 3x stubs  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 
 
 
 
 
 
 
 Because we didn't want to maintain documentation in two places, many of the core Puppet functions are implemented in the 4x style but have a matching 3x stub with contains all the documentation. We need to ensure that strings can handle this in a way that makes sense, combining the relevant information from both, taking only the doc string from the 3x version, or something similar. h4. Example:h5. The 4.x implementation of {{contain}} in {{lib/puppet/functions/contain.rb}}:{code}# Called within a class definition, establishes a containment# relationship with another class# For documentation, see the 3.x stub#Puppet::Functions.create_function(:contain, Puppet::Functions::InternalFunction) do...{code}h5. The 3.x stub of {{contain}} in {{lib/puppet/parser/functions/contain.rb}}:{code}# Called within a class definition, establishes a containment# relationship with another classPuppet::Parser::Functions::newfunction(  :contain,  :arity => -2,  :doc => "Contain one or more classes inside the current class. If any of...) do |classes|  # Call the 4.x version of this function in case 3.x ruby code uses this function  Puppet.warn_once(:deprecation, '3xfunction#contain', "Calling function_contain via the Scope class is deprecated. Use Scope#call_function instead")  call_function('contain', classes)end{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are 

Jira (PUP-6087) Multiple contradictory 'consumes' annotation do not lead to an error

2016-09-14 Thread Susan McNerney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Susan McNerney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6087 
 
 
 
  Multiple contradictory 'consumes' annotation do not lead to an error  
 
 
 
 
 
 
 
 
 

Change By:
 
 Susan McNerney 
 
 
 

Sprint:
 
 AO 2016-08-10, AO 2016-08-24, AO 2016-09-07 , bugs under investigation 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6182) Application declarations don't properly validate component mappings

2016-09-14 Thread Susan McNerney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Susan McNerney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6182 
 
 
 
  Application declarations don't properly validate component mappings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Susan McNerney 
 
 
 

Sprint:
 
 AO 2016-08-10, AO 2016-08-24, AO 2016-09-07 , bugs under investigation 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6497) CapabilityFinder says a capability couldn't be found if there are multiple versions of it

2016-09-14 Thread Susan McNerney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Susan McNerney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6497 
 
 
 
  CapabilityFinder says a capability couldn't be found if there are multiple versions of it  
 
 
 
 
 
 
 
 
 

Change By:
 
 Susan McNerney 
 
 
 

Sprint:
 
 AO 2016-08-10, AO 2016-08-24, AO 2016-09-07 , bugs under investigation 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6701) PE Everett fails to install: Unknown function: 'puppetdb_query'

2016-09-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  PUP-6701 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PE Everett fails to install: Unknown function: 'puppetdb_query'  
 
 
 
 
 
 
 
 
 
 
Joshua Partlow It looks like not - possibly that nightly pipeline run just started before the pez enablement landed? I'll look in to if the run that John kicked gets pezzed, and dig deeper if it's not a thing. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-94) Strings crashes when documenting defined type with parameters with types

2016-09-14 Thread Jason Kincl (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kincl commented on  PDOC-94 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Strings crashes when documenting defined type with parameters with types  
 
 
 
 
 
 
 
 
 
 
Will do, thanks for the update Henrik! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6701) PE Everett fails to install: Unknown function: 'puppetdb_query'

2016-09-14 Thread Christopher Thorn (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Thorn commented on  PUP-6701 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PE Everett fails to install: Unknown function: 'puppetdb_query'  
 
 
 
 
 
 
 
 
 
 
Just talked with John Duarte, he has kicked off the nightly CI job puppet-agent. Once that passes, in about six hours, promotion should be good to go for this fix.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6697) Allow full downloaded CA bundle to be stored to agent's localcacert file

2016-09-14 Thread Karen Van der Veer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6697 
 
 
 
  Allow full downloaded CA bundle to be stored to agent's localcacert file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Team:
 
 Engineering "Pool" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6701) PE Everett fails to install: Unknown function: 'puppetdb_query'

2016-09-14 Thread Joshua Partlow (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Partlow commented on  PUP-6701 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: PE Everett fails to install: Unknown function: 'puppetdb_query'  
 
 
 
 
 
 
 
 
 
 
We did get a bump last night to puppet-agent 1.6.2-172, 04cc4283d93686b528c02c0f9729b7a816cc1bcf, which Kerminator assures me contains puppet 4.6.2-154-gbcd1654, which does not have Henrik's patch from yesterday. 
The head of puppet/master is at 4.6.2-162-g5bb93f0; does anyone know when that will make it through into a puppet-agent to be promoted? 
Branan Riley oh, the fact that we got a new puppet-agent without the patch promoted makes me wonder if pez didn't actually run after all? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6702) Windows service in Paused state cannot be managed

2016-09-14 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6702 
 
 
 
  Windows service in Paused state cannot be managed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Sub-team:
 
 Platforms 
 
 
 

Sprint:
 
 APS Triage 
 
 
 
 
 
 
 
 
 
  When a service is in the Paused state; it's 'ensure' property cannot be managed by PuppetNote that for our own services that use nssm; nssm has a characteristic that it uses the "Paused" service state for a service that has reached a fault state (see https://nssm.cc/usage )*To reproduce:* * Install puppet-agent * Ensure pxp-agent service is stopped in services.msc * Ensure the ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf file is renamed or deleted * Run _puppet resource service pxp-agent ensure=running_The service will now be in the paused state. Attempting _puppet resource service pxp-agent ensure=stopped_ will echo back ensure=stopped , but services.msc will show the service as still paused. Attempting _puppet resource service pxp-agent ensure=running_ will return an error:{noformat}C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Puppet>puppet resource service pxp-agent ensure=runningError: Cannot start pxp-agent, error was: Execution of 'C:/Windows/system32/net.exe start pxp-agent' returned 2: The requested service has already been started.More help is available by typing NET HELPMSG 2182.Wrapped exception:Execution of 'C:/Windows/system32/net.exe start pxp-agent' returned 2: The requested service has already been started.More help is available by typing NET HELPMSG 2182.Error: /Service[pxp-agent]/ensure: change from stopped to running failed: Cannot start pxp-agent, error was: Execution of 'C:/Windows/system32/net.exe start pxp-agent' returned 2: The requested service has already been started.More help is available by typing NET HELPMSG 2182.{noformat}Outside of Puppet, the service can be stopped by simply using the Stop option in services.msc*Expected behaviour:* * The "Paused" state should be understood by Puppet for a Windows service resource. Or at least; Puppet should actually stop a service in the "Paused" state when ensure=stopped is applied. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
   

Jira (PDOC-94) Strings crashes when documenting defined type with parameters with types

2016-09-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PDOC-94 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Strings crashes when documenting defined type with parameters with types  
 
 
 
 
 
 
 
 
 
 
Thanks for the report - we are aware of many errors in the current version of Puppet Strings. A major overhaul and update to a later yard is in the process. We are planning to have a new release of Puppet Strings shortly. When that is out it would be great if you could test if this is then still a problem. 
Stay tuned... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1356) External facts should be able to return structured data

2016-09-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1356 
 
 
 
  External facts should be able to return structured data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Sprint:
 
 Client 2016-09-07,  Client  APS  2016-09-21 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1356) External facts should be able to return structured data

2016-09-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1356 
 
 
 
  External facts should be able to return structured data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Team:
 
 Agent & Platform Support 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1356) External facts should be able to return structured data

2016-09-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1356 
 
 
 
  External facts should be able to return structured data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1497) system_uptime fact only updates every minute on Solaris and AIX

2016-09-14 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  FACT-1497 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: system_uptime fact only updates every minute on Solaris and AIX  
 
 
 
 
 
 
 
 
 
 
This limitation is also true for AIX systems. Verified on AIX 5.3, 6.1, 7.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1497) system_uptime fact only updates every minute on Solaris and AIX

2016-09-14 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1497 
 
 
 
  system_uptime fact only updates every minute on Solaris and AIX  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 The {{system_uptime}} fact does not update as expected on Solaris  10  and AIX . Once a value is retrieved for the fact, it remains cached without updating the second value.h3. Steps to recreate# Install puppet-agent 1.6.1# Run {{facter system_uptime.seconds}} to load initial value# Rerun {{facter system_uptime.seconds}} repeatedly to see that the same value is repeatedly returned without incrementing.# Wait 30 seconds# Rerun {{facter system_uptime.seconds}} to see updated valueh3. Sample session  on Solaris 10 {code}Oracle Corporation  SunOS 5.10  Generic Patch   January 2005-bash-3.2# cat /opt/puppetlabs/bin/ facter/  mcollective/ puppet/  pxp-agent/-bash-3.2# cat /opt/puppetlabs/puppet/VERSION1.6.1-bash-3.2# facter --version3.4.1 (commit d0f32490f41ca12722c13e4c48d4572ae4f9bfdc)-bash-3.2# facter system_uptime.seconds; sleep 2; facter system_uptime.seconds150120150120-bash-3.2# facter system_uptime.seconds; sleep 2; facter system_uptime.seconds150120150120-bash-3.2# facter system_uptime.seconds; sleep 30; facter system_uptime.seconds150120150180-bash-3.2# facter system_uptime.seconds; sleep 29; facter system_uptime.seconds150180150180{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1497) system_uptime fact only updates every minute on Solaris and AIX

2016-09-14 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1497 
 
 
 
  system_uptime fact only updates every minute on Solaris and AIX  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Summary:
 
 system_uptime fact only updates every  30 seconds  minute  on Solaris  and AIX 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6291) Add 'abs' support to Numeric.new

2016-09-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6291 
 
 
 
  Add 'abs' support to Numeric.new  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Acceptance Criteria:
 
 That an optional (second) boolean argument to the new method on Integer, Float or Numeric makes the conversion to a number return an absolute value if the boolean is {{true}} and a positive or negative value (depending on the input) otherwise. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6291) Add 'abs' support to Numeric.new

2016-09-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6291 
 
 
 
  Add 'abs' support to Numeric.new  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 It is now possible to specify that an absolute (positive) value is wanted when creating a new Integer, Float, or abstractly via Numeric by passing a second optional boolean argument to the {{new}} function where {{true}} means that an absolute value is wanted. For example {{Numeric.new($str, true)}} which converts the numerical value in string form (with a possible leading minus) to an absolute value. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-94) Strings crashes when documenting defined type with parameters with types

2016-09-14 Thread Jason Kincl (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kincl updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-94 
 
 
 
  Strings crashes when documenting defined type with parameters with types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Kincl 
 
 
 

Environment:
 
 * puppet-agent-1.6.2-1.el7.x86_64 {code}package { ' * yard ':  ensure => [' 0.8.7 '],  }package { ' * puppet-strings ':  ensure => [' 0.4.0 '],  }{code} * RHEL 7 x86_64 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-94) Strings crashes when documenting defined type with parameters with types

2016-09-14 Thread Jason Kincl (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kincl updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-94 
 
 
 
  Strings crashes when documenting defined type with parameters with types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Kincl 
 
 
 

Environment:
 
 puppet-agent-1.6.2-1.el7.x86_64 {code:java} package { 'yard':  ensure => ['0.8.7'],}package { 'puppet-strings':  ensure => ['0.4.0'],} {code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-94) Strings crashes when documenting defined type with parameters with types

2016-09-14 Thread Jason Kincl (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kincl updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-94 
 
 
 
  Strings crashes when documenting defined type with parameters with types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Kincl 
 
 
 

Environment:
 
 puppet-agent-1.6.2-1.el7.x86_64{code :java }package { 'yard':  ensure => ['0.8.7'],}package { 'puppet-strings':  ensure => ['0.4.0'],}{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDOC-94) Strings crashes when documenting defined type with parameters with types

2016-09-14 Thread Jason Kincl (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kincl created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-94 
 
 
 
  Strings crashes when documenting defined type with parameters with types  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PDOC 0.4.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 DOCS 
 
 
 

Created:
 

 2016/09/14 7:08 AM 
 
 
 

Environment:
 
 
puppet-agent-1.6.2-1.el7.x86_64 
package  { 'yard': ensure => ['0.8.7'], } 
package  { 'puppet-strings': ensure => ['0.4.0'], } 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Jason Kincl 
 
 
 
 
 
 
 
 
 
 
Running strings on a defined type with a type results in a stack trace. 
 
 
 
 
 
 
$ puppet strings yardoc 

Jira (PUP-6291) Add 'abs' support to Numeric.new

2016-09-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6291 
 
 
 
  Add 'abs' support to Numeric.new  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-5834) Handle extended data in the catalog

2016-09-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5834 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Handle extended data in the catalog  
 
 
 
 
 
 
 
 
 
 
I think we have conversion for two reasons; arguments / parameter values when creating resources, and when calling 3.x functions. We should continue to transform values for 3.x function calls after this change (or they will start breaking). 
Timespan and Timestamp have not been released yet, so no users could possibly have been using those with the expectation that they transform to strings. For SemVer, SemVerRange it is different as users may have adopted using those and then relying on the transformation to turn it into a string. There are resource types that deal with version in string format. For Regexp since it has been in the language for a long time that there are users who rely on the transformation - however, before 4.x / future-parser it was not possible to get an actual regular _expression_ into a variable, or into a resource, so the risk is minimal. 
The tricky thing here is that it is really the resource type and the providers that must be prepared to deal with the richer data type. There can be logic both in the type and in the provider that needs to be changed. To cover all bases: 
 

Send rich data in catalog for types that supports this 
 

This means adding a feature to the Resource API to allow the type to turn this on
 

We need to add support for that in the pcore representation of a resource type
 
 
 

A provider that can handle rich data types should declare that it has this feature/capability 
 

The type's API would then, if the selected provider does not support rich data types (when the type does), needs to transform the rich data types to strings (like we now do).
 
 
 
 
This could possibly be simplified so that rich data is always sent. On the agent side (unless the type supports rich data) the transformation to strings takes place as part of deserialization/instantiation. We still need to deal with providers. 
That is a massive amount of conditional logic for the purpose of guarding against a fairly small risk (basically getting a Regexp instead of a string since the rest of the types are not yet in general use). Our implementation of this is brand new and it should be considered experimental at first. Therefore it seems reasonable to simply use a feature flag. That will enable us to learn how this works in practice and if we need to add the more elaborate scheme of supporting opt in per type and provider, or if it is simply a matter of "don't send rich data types to resource types that do not support that" - it is more or less the 

Jira (PUP-5834) Handle extended data in the catalog

2016-09-14 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-5834 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Handle extended data in the catalog  
 
 
 
 
 
 
 
 
 
 
Do we need some kind of feature-switch to enable this functionality in 4.y? For instance, the Puppet::Pops::Evaluator::Runtime3Converter will currently convert Regexp, SemVer, SemVerRange, Timespan, and Timestamp into strings. It won't need to once ext_parameters support is enabled but I guess changing that behavior must be considered a breaking change? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6291) Add 'abs' support to Numeric.new

2016-09-14 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6291 
 
 
 
  Add 'abs' support to Numeric.new  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-5831) Add a Binary type and runtime object

2016-09-14 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5831 
 
 
 
  Add a Binary type and runtime object  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments

2016-09-14 Thread Kevin Corcoran (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Corcoran commented on  PUP-731 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments  
 
 
 
 
 
 
 
 
 
 
We also have PE-16821 which captures the work for PE Everett in Puppet Server and file sync to automatically call puppet generate types when necessary.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-731) Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments

2016-09-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-731 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Masters cannot reliably distinguish between multiple versions of a type/function/plugin used in different environments  
 
 
 
 
 
 
 
 
 
 
I believe SERVER-94 is the ticket for the remaining work on the Puppet Server side. 
The state of Ruby code isolation in general in Puppet > 4.6.2 is: 
 

4.x functions are safe provided the rules documented in the 4.x function API are followed (for example, do not bind to Ruby constants)
 

3.x functions are safe, but not if they have external helper code (same rules as for 4.x apply, no binding to constants etc.)
 

Resource types are safe provided that the generate types command has been run (manually or automatically by Puppet Server). Here, if user changes implementation, the command must be executed again. The result is that no ruby code is loaded for the resource types
 

Helper code - helper Ruby code that is not inside of functions is not safe. It must be handled as an extension to puppet (i.e. the same version used in all environments, just like any other gem used by puppet).
 
 
We know we need to work on the documentation and messaging around env isolation support. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6702) Windows service in Paused state cannot be managed

2016-09-14 Thread James Stocks (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Stocks created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6702 
 
 
 
  Windows service in Paused state cannot be managed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.6.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Windows 
 
 
 

Created:
 

 2016/09/14 3:33 AM 
 
 
 

Environment:
 
 
TEST_TARGET=windows2008r2-64a SUITE_VERSION=1.6.2.135.g8a48f21 SUITE_COMMIT=8a48f210f6901be0edba16eb49c1bfbfb07d338b 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 James Stocks 
 
 
 
 
 
 
 
 
 
 
When a service is in the Paused state; it's 'ensure' property cannot be managed by Puppet 
Note that for our own services that use nssm; nssm has a characteristic that it uses the "Paused" service state for a service that has reached a fault state (see https://nssm.cc/usage ) 
To reproduce: 
 

Install puppet-agent
 

Jira (PDB-3052) [QA] Identify Tests Required

2016-09-14 Thread Seamus McKenna (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Seamus McKenna created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3052 
 
 
 
  [QA] Identify Tests Required  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 
 Andrew Hayes 
 
 
 

Components:
 

 QA 
 
 
 

Created:
 

 2016/09/14 3:05 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Seamus McKenna 
 
 
 
 
 
 
 
 
 
 
Identify tests required Add to PDB Pipeline if required 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)