Jira (PUP-6803) puppet run status should be "failed" if there are failed generated resources

2016-10-13 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-6803 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet run status should be "failed" if there are failed generated resources  
 
 
 
 
 
 
 
 
 
 
initial PR raised 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1441) Add "cloud" or similar fact that identifies AWS, Azure, etc

2016-10-13 Thread Scott McClellan (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott McClellan updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1441 
 
 
 
  Add "cloud" or similar fact that identifies AWS, Azure, etc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Scott McClellan 
 
 
 
 
 
 
 
 
 
 We should add a fact that determines whether or not a VM is running in Azure .Fact structure : {code}"virtualization": { "hypervisor": "kvm", "cloud": {"provider": "azure" }}{code}Note that {{hypervisor}} above is the same as the {{virtual}} fact. * *How to calculate whether a machine is running in Azure*** Windows* {code}$systemEnclosure = Get-WmiObject -class Win32_SystemEnclosure -namespace root\CIMV2$computerSystemProduct = Get-WmiObject -class Win32_ComputerSystemProduct -namespace root\CIMV2'ChassisAssetTag:   "{0}"' -f $systemEnclosure.SMBIOSAssetTag{code}*Expected Results*{code}"7783-7084-3265-9085-8269-3286-77"{code}*Linux*{code}sudo dmidecode | grep "Asset Tag: 7783-7084-3265-9085-8269-3286-77"{code}*Expected Results*{code}Asset Tag: 7783-7084-3265-9085-8269-3286-77{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 (FACT-1441) Add "virtualization" fact that identifies AWS, Azure, etc

2016-10-13 Thread Scott McClellan (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott McClellan updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1441 
 
 
 
  Add "virtualization" fact that identifies AWS, Azure, etc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Scott McClellan 
 
 
 

Summary:
 
 Add " cloud virtualization "  or similar  fact that identifies AWS, Azure, etc 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6807) referencing non-existant variable in custom function crashes puppetserver

2016-10-13 Thread Justin Stoller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Stoller commented on  PUP-6807 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: referencing non-existant variable in custom function crashes puppetserver  
 
 
 
 
 
 
 
 
 
 
The fix was merged into Puppet at: 2fe2216 and was promoted into puppet-agent at: fa70f7b which passed a full CI run here: puppet-agent (master) Suite Pipeline Step 7 – Puppet Tests : Build 232 
Closing as complete. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1517) Building against boost 1.62 fails

2016-10-13 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1517 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Building against boost 1.62 fails  
 
 
 
 
 
 
 
 
 
 
That seems likely that you're linking against Leatherman built using Boost 1.61. I don't reproduce that problem with a build using the fix for LTH-115. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6815) Reserved characters in class/type parameters are not enforced

2016-10-13 Thread Rob Nelson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson commented on  PUP-6815 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reserved characters in class/type parameters are not enforced  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg Hrm, I don't see in there where the valid characters in a parameter name are defined, that's what I was looking for. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3068) Make sure we have full-stack retry->dlo test(s)

2016-10-13 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning assigned an issue to Rob Browning 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3068 
 
 
 
  Make sure we have full-stack retry->dlo test(s)  
 
 
 
 
 
 
 
 
 

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 (PUP-6815) Reserved characters in class/type parameters are not enforced

2016-10-13 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6815 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reserved characters in class/type parameters are not enforced  
 
 
 
 
 
 
 
 
 
 
That is about variables - all details about parameters is here: https://github.com/puppetlabs/puppet-specifications/blob/cc7861867aeaca1047fc34d4c4fbeba4e79efb7c/language/parameter_scope.md Then there are the expressions that operate on resources.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6245) Acceptance: fix zpool create zone test

2016-10-13 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6245 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Acceptance: fix zpool create zone test  
 
 
 
 
 
 
 
 
 
 
Kurt Wall Will you be managing the merge up from stable to master for this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6245) Acceptance: fix zpool create zone test

2016-10-13 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to Kurt Wall 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6245 
 
 
 
  Acceptance: fix zpool create zone test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Assignee:
 
 Kurt Wall 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1518) Facter does not correctly quote keys of `ttls` list when querying cpp-hocon

2016-10-13 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  FACT-1518 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter does not correctly quote keys of `ttls` list when querying cpp-hocon  
 
 
 
 
 
 
 
 
 
 
Assigning to Brannan as he did the merge. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6245) Acceptance: fix zpool create zone test

2016-10-13 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6245 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Acceptance: fix zpool create zone test  
 
 
 
 
 
 
 
 
 
 
Merged into stable at; https://github.com/puppetlabs/puppet/commit/5fd37e3e4aabc5c7ee94b884216ec695e3a9ef55 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1518) Facter does not correctly quote keys of `ttls` list when querying cpp-hocon

2016-10-13 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  FACT-1518 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter does not correctly quote keys of `ttls` list when querying cpp-hocon  
 
 
 
 
 
 
 
 
 
 
Merged into master at; https://github.com/puppetlabs/facter/commit/cfeac3d3218abd1e30f230b76d5474e054a8bd24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1518) Facter does not correctly quote keys of `ttls` list when querying cpp-hocon

2016-10-13 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1518 
 
 
 
  Facter does not correctly quote keys of `ttls` list when querying cpp-hocon  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

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-6817) Improve how corrective_change is determined for exec resource

2016-10-13 Thread James Stocks (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Stocks created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6817 
 
 
 
  Improve how corrective_change is determined for exec resource  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Client 
 
 
 

Created:
 

 2016/10/13 1:05 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 James Stocks 
 
 
 
 
 
 
 
 
 
 
Raising this as an enhancement rather than a bug; as the current behaviour has been reviewed and accepted as a document item (PE-17036) 
Current behaviour: 
If I have an exec resource with a descriptive title like: 
 
 
 
 
 
 
  exec { 'My important log file' : 
 
 
 
 
command => '/usr/bin/touch /tmp/logfile', 
 
 
 
 
unless  => '/usr/bin/test -e /tmp/logfile', 

Jira (PDB-3098) Remove ActiveMQ/KahaDB related docs

2016-10-13 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3098 
 
 
 
  Remove ActiveMQ/KahaDB related docs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/10/13 12:43 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ryan Senior 
 
 
 
 
 
 
 
 
 
 
We have some stale docs with the stockpile work as users no longer need to be concerned with KahaDB corruption, AcitveMQ tuning etc. This ticket covers going through the docs and removing/updating/changing those as necessary.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PDOC-93) Search box overlaps list items below on lefthand fulldoc navigator

2016-10-13 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-93 
 
 
 
  Search box overlaps list items below on lefthand fulldoc navigator  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6815) Reserved characters in class/type parameters are not enforced

2016-10-13 Thread Rob Nelson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson commented on  PUP-6815 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reserved characters in class/type parameters are not enforced  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg That would specifically be this section, correct? (assumption: as it says in the paragraphs above, parameters are just variables in a certain location and the same rules apply to them) https://github.com/puppetlabs/puppet-specifications/blob/cc7861867aeaca1047fc34d4c4fbeba4e79efb7c/language/types_values_variables.md#variable-names 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-93) Search box overlaps list items below on lefthand fulldoc navigator

2016-10-13 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-93 
 
 
 
  Search box overlaps list items below on lefthand fulldoc navigator  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-120) Generated _index.html page is not accessible on github.io

2016-10-13 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-120 
 
 
 
  Generated _index.html page is not accessible on github.io  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 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 (PDOC-120) Generated _index.html page is not accessible on github.io

2016-10-13 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PDOC-120 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Generated _index.html page is not accessible on github.io  
 
 
 
 
 
 
 
 
 
 
PR is up at https://github.com/puppetlabs/puppet-strings/pull/115 
We don't even actually have to turn Jekyll off. I just added a bit to the rake task to add a Jekyll _config.yml file with include: _index.html, which just allows the file to be published. That config only ends up in the doc directory of the gh_pages branch. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-128) Update README to explain: What's the deal with @example tags?

2016-10-13 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-128 
 
 
 
  Update README to explain: What's the deal with @example tags?  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-120) Generated _index.html page is not accessible on github.io

2016-10-13 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PDOC-120 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Generated _index.html page is not accessible on github.io  
 
 
 
 
 
 
 
 
 
 
merged to master at: bda361a 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6815) Reserved characters in class/type parameters are not enforced

2016-10-13 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6815 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reserved characters in class/type parameters are not enforced  
 
 
 
 
 
 
 
 
 
 
It is a bug in the documentation afaict, and has always been a bug in the documentation. Parameter names are bare words, or keywords, and they support more than what is listed as acceptable names in the documentation. Look at the specification instead of the documentation. Parameter names cannot start with an upper case letter (as that makes it a type reference) nor with an underscore because those are considered private to the context they are defined in. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6474) Incorporate gettext_setup gem into puppet

2016-10-13 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  PUP-6474 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Incorporate gettext_setup gem into puppet  
 
 
 
 
 
 
 
 
 
 
Due to the ongoing work in SERVER-1412, this can't be rolled out entirely. I've submitted a PR that enables gettext in all situations except when run as part of puppet-server. Making it work in puppet-server is ticketed as SERVER-1593 and PUP-6816. 
This (somewhat hackish) PR will unblock the rest of the POC, and can be reverted when puppet-server gem installation is unblocked 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6816) Make gettext a hard requirement

2016-10-13 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6816 
 
 
 
  Make gettext a hard requirement  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP 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 (PUP-6816) Make gettext a hard requirement

2016-10-13 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6816 
 
 
 
  Make gettext a hard requirement  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/10/13 11:34 AM 
 
 
 

Fix Versions:
 

 PUP 4.8.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
in PUP-6474, we worked around SERVER-1412 by making the gettext-setup gem optional. This is a nasty hack, and should be removed before we ship. Once the work of getting gettext-setup into server is done, we can clean this up. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
  

Jira (PDOC-120) Generated _index.html page is not accessible on github.io

2016-10-13 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-120 
 
 
 
  Generated _index.html page is not accessible on github.io  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Release Notes Summary:
 
 Previously when using the strings:gh_pages:update rake task, the generated _index.html file was not accessible in the published documentation. This change adds a configuration option to the project to allow the file to be published. 
 
 
 

Release Notes:
 
 Bug 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 (PDOC-120) Generated _index.html page is not accessible on github.io

2016-10-13 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-120 
 
 
 
  Generated _index.html page is not accessible on github.io  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Acceptance Criteria:
 
 After using the GH pages rake task as instructed by the README, the _index.html file should be accessible on the published GH site. 
 
 
 

Story Points:
 
 1 
 
 
 

Team:
 
 Puppet Developer Support 
 
 
 

Sprint:
 
 PDS 2016-10-19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

Jira (PDOC-120) Generated _index.html page is not accessible on github.io

2016-10-13 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper assigned an issue to William Hopper 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-120 
 
 
 
  Generated _index.html page is not accessible on github.io  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Assignee:
 
 William Hopper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1384) Remove deprecated APIs necessitated by Server 2003 compat

2016-10-13 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1384 
 
 
 
  Remove deprecated APIs necessitated by Server 2003 compat  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Fix Version/s:
 
 FACT 3.y 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3042) If a catalog has a dependency cycle, it does not count as failed

2016-10-13 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3042 
 
 
 
  If a catalog has a dependency cycle, it does not count as failed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Labels:
 
 needs_repro 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6524) The shell used with exec resource provider=shell should be configurable

2016-10-13 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6524 
 
 
 
  The shell used with exec resource provider=shell should be configurable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Component/s:
 
 Client 
 
 
 

Component/s:
 
 Types and Providers 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6184) Remove win32-dir code usage from Puppet / Facter

2016-10-13 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6184 
 
 
 
  Remove win32-dir code usage from Puppet / Facter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1384) Remove deprecated APIs necessitated by Server 2003 compat

2016-10-13 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1384 
 
 
 
  Remove deprecated APIs necessitated by Server 2003 compat  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Labels:
 
 Maintenance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1384) Remove deprecated APIs necessitated by Server 2003 compat

2016-10-13 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1384 
 
 
 
  Remove deprecated APIs necessitated by Server 2003 compat  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP 2016-10-19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (HI-539) Hierarchies are being ignored

2016-10-13 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  HI-539 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hierarchies are being ignored  
 
 
 
 
 
 
 
 
 
 
Tom De Vylder, the behavior above would be exactly what you get if you have a global hiera.yaml that uses interpolation of % {environmentpath} 
 to find data in the environiment. Are you 100% sure that isn't the case? I'm certain that the environment data provider is never consulted. If it was, that would have shown in the explain output as "Data Provider "Hiera Data Provider, version 4". That's regardless of if it finds the key or not. But it doesn't go beyond the global "Hiera" at the top. The key is found there. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1384) Remove deprecated APIs necessitated by Server 2003 compat

2016-10-13 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1384 
 
 
 
  Remove deprecated APIs necessitated by Server 2003 compat  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP 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 (PUP-6184) Remove win32-dir code usage from Puppet / Facter

2016-10-13 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6184 
 
 
 
  Remove win32-dir code usage from Puppet / Facter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP 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 (PUP-3732) type validation should not run for `puppet resource`

2016-10-13 Thread Ben Roberts (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Roberts commented on  PUP-3732 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: type validation should not run for `puppet resource`  
 
 
 
 
 
 
 
 
 
 
Having just lost about 6 hours to debugging this exact same issue, issue still present in 4.7.0. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-10-13 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5831 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add a Binary type and runtime object  
 
 
 
 
 
 
 
 
 
 
The ruby example creates a string with three bytes 66, 67, 68. The puppet example Binary([66,67,68]) does the same, only that the string buffer is internal to the Binary and the created binary instance manifests itself in string form using base64 as opposed to the Ruby string which becomes the character/text representation of those bytes in the Ruby string encoding (in the example that would be ASCII-8Bit). There is no way in puppet to take a Binary and turn it into a textual representation in some other encoding. 
It is possible to create a Binary from a String that is in any encoding - but not the reverse as that would expose the concept of string encoding in the puppet language. 
A ByteInteger is a type only available locally in the function that creates an instance. It is simply an integer value 0-255. 
You cannot create byte-packed ints in puppet, if by that you mean that two 64bit integers would be represented as 8 bytes in big or small endian format. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-10-13 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-5831 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add a Binary type and runtime object  
 
 
 
 
 
 
 
 
 
 
aha. like this? 
 
 
 
 
 
 
[root@y2j8yb0r6kahjvd ~]# puppet apply -e 'notice(Binary([66,67]),"%s")' 
 
 
 
 
Notice: Scope(Class[main]): QkM= %s
 
 
 
 
 
 
 
but with that encoding as string, shouldn't that be BD? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (HI-539) Hierarchies are being ignored

2016-10-13 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-539 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hierarchies are being ignored  
 
 
 
 
 
 
 
 
 
 
To rule out the lookup CLI, can you try with a manifest and using puppet apply? I would like to see what a notice hiera(key) does in your case (since that uses only your global hiera configuration). Then try with a notice lookup(key) which uses both the global hiera, env, and modules. 
If you are certain there is nothing for the key in global hiera, and it does not continue with env, or a module - then there must be something wrong with the configuration (or that it uses an environment other than the one where you have the configuration) as it does not seem to take effect. 
You may also want to hop onto Slack or IRC and get interactive help from the community as that may help you resolve the issues faster. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-10-13 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-5831 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add a Binary type and runtime object  
 
 
 
 
 
 
 
 
 
 
sorry, i meant  
when the acceptance criteria says: 
 
 

It should be possible to create a Binary from:
 

[...]
 

an Array of integer byte values, including an empty array
 
 
 
how does one create byte ints in puppet? 
i've tried things like:  
 
 
 
 
 
 
[root@d985o84d944gf9o ~]# puppet apply -e 'notice (Binary(Array([66,67]),"%B"))' 
 
 
 
 
Error: Evaluation Error: Error while evaluating a Function Call, 'new_Binary' expects one of: 
 
 
 
 
  (String str, Base64Format = Enum['%B', '%b', '%r', '%s', '%u'] format?) 
 
 
 
 
rejected: parameter 'str' expects a String value, got Tuple 
 
 
 
 
  (Array[ByteInteger] byte_array) 
 
 
 
 
rejected: expects 1 argument, got 2 
 
 
 
 
  (BinaryArgsHash = Variant[StringHash = Struct[{'value' => String, 'format' => Optional[Base64Format = Enum['%B', '%b', '%r', '%s', '%u']]}], 

Jira (PUP-6815) Reserved characters in class/type parameters are not enforced

2016-10-13 Thread Rob Nelson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson commented on  PUP-6815 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reserved characters in class/type parameters are not enforced  
 
 
 
 
 
 
 
 
 
 
I believe this is a bug in puppet, not the docs, as the docs show a consistent intent going back to v2.7 that parameter names must not contain uppercase characters (https://github.com/puppetlabs/puppet-docs/blob/2e0eacbe0c8e8b288ca10313920b3ae0fda9d3ed/source/puppet/2.7/reference/lang_reserved.markdown). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6815) Reserved characters in class/type parameters are not enforced

2016-10-13 Thread Rob Nelson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6815 
 
 
 
  Reserved characters in class/type parameters are not enforced  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.7.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/10/13 8:15 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Nelson 
 
 
 
 
 
 
 
 
 
 
Per https://docs.puppet.com/puppet/latest/reference/lang_reserved.html#parameters, parameter names cannot contain capitalized characters (\A\$[a-z][a-z0-9_]*\Z). This is not enforced by puppet: 
 
 
 
 
 
 
[rnelson0@build03]$ cat test.pp 
 
 
 
 
class test ( 
 
 
 
 
  $param_one = false, 
 
 
 
  

Jira (HI-539) Hierarchies are being ignored

2016-10-13 Thread Tom De Vylder (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom De Vylder commented on  HI-539 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hierarchies are being ignored  
 
 
 
 
 
 
 
 
 
 
The particular data I was testing with is stored in $ {environment} 
/hieradata only. It shouldn't match in global Hiera nor in modules. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2931) Investigate metrics needs for the new queue

2016-10-13 Thread Ryan Senior (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior commented on  PDB-2931 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Investigate metrics needs for the new queue  
 
 
 
 
 
 
 
 
 
 
We do have the time to persist to the queue, it's "message-persistence-time". We're keeping the commands per second as well. 
So it seems like what I should add 
 

the duration the message is in the queue
 

histogram on the size of the messages (as reported by the content-length header)
 
 
It also occurred to me that we don't currently have a metric around how many commands are currently delayed and waiting to be retried, that seems useful, and it's pretty easy to add. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (HI-539) Hierarchies are being ignored

2016-10-13 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-539 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hierarchies are being ignored  
 
 
 
 
 
 
 
 
 
 
Thomas pointed out that the explain is telling us that it finds the value using the global hierarchy in hiera. Lookup is designed that way - using priority lookup (as is the case here) if a value is found in hiera that value is used and it never continues into the env or module data providers. Thus, you must ensure that the value is not found there - see class hiera as an override over all other data - there is no merge of all hierarchical levels in the three tiers; global, env, module - they can have their own hierarchy and they do not blend. 
The --node is an option designed to provide lookup from the perspective of that node (what is known about it). If you don't want that, the values must be provided via the --facts option 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (HI-539) Hierarchies are being ignored

2016-10-13 Thread Tom De Vylder (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom De Vylder commented on  HI-539 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hierarchies are being ignored  
 
 
 
 
 
 
 
 
 
 
Apparently it makes a rather big difference whether or not the value of "--node" is known to Puppet. I've been testing mostly with just 'node01' instead of an actual hostname because it's just way faster to run 'puppet lookup' than it is to have an agent run. And typing 'node01' requires less keystrokes than an actual hostname. 
Even though I wasn't using anything that matches $trusted.certname it still wouldn't find very generic data in f.i. hieradata/common.yaml. Whether or not the node is known to Puppet it should still match fall-back hierarchies. Or throw an error. So I think that part is a bug. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-10-13 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5831 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add a Binary type and runtime object  
 
 
 
 
 
 
 
 
 
 
Creating a Binary from an empty Array creates an empty Binary. An empty string in base64 encoding is also an empty string. 
Eric Thompson I think I am missing something - what is the "maybe you meant..." a reference to? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.