Jira (PUP-6920) Windows package provider should set working directory (cwd)

[Ethan Brown (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6920 
 
 
 
  Windows package provider should set working directory (cwd)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/15 10:54 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 
Some installations may require files other than the installer to install properly. The assumption of these installation packages may be that the path to these files is the current working directory. 
However, the Windows package provider currently does not set a working directory - and hence cannot currently support certain types of installations. 
PUP-6919 tracks the work to support cwd with the underlying Puppet::Util::Execution.execute mechanism. This ticket is to track setting the cwd automatically to the same location as the installer source. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 

Jira (PUP-6919) Puppet::Util::Windows::Process.execute should accept a working directory

[Ethan Brown (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6919 
 
 
 
  Puppet::Util::Windows::Process.execute should accept a working directory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Team:
 
 Agent & 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 (PUP-6919) Puppet::Util::Windows::Process.execute should accept a working directory

[Ethan Brown (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6919 
 
 
 
  Puppet::Util::Windows::Process.execute should accept a working directory  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/15 10:51 PM 
 
 
 

Labels:
 

 windows package 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 
The Windows API supports setting a working directory when starting a process. However, Puppet does not currently allow setting this value programatically. 
The win32-process gem can pass cwd supplied through it's argument hash - see code at https://github.com/djberg96/win32-process/blob/win32-process-0.7.5/lib/win32/process.rb#L681 
Puppet currently uses Dir.chdir to set a working directory before creating a process - however, this might not always work properly on Windows. The cwd has File.directory?(dir) used to validate it, which could fail on UNC or other path types on Windows - meaning that Dir.chdir at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/exec.rb#L29 never gets called as expected. 
cwd should be passed in to Puppet::Util::Execution.execute at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/exec.rb#L59 / and the call to Process.create at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/process.rb#L12 should pass the arguments value through. 
 
 
 
 
 
 
 
   

Jira (PUP-6188) Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8

[Ethan Brown (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-6188 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8  
 
 
 
 
 
 
 
 
 
 
An addendum regarding SSL files - some files may have comments, which must be in UTF-8. For instance, RFC 4716 for the "Public Key File Format" says that header values may contain UTF-8. So it may be best to use UTF-8 for all SSH files after all to be on the safe side. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6918) SSL - Improve CSR to local public key mismatch handling

[Ethan Brown (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6918 
 
 
 
  SSL - Improve CSR to local public key mismatch handling  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.8.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/15 9:41 PM 
 
 
 

Labels:
 

 ssl 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ethan Brown 
 
 
 
 
 
 
 
 
 
 
Assume the following sequence of events: 
 

Agent has generated public / private key pair and a CSR
 

Agent has sent a CSR to the master (by way of a `puppet agent` run)
 

Master has not yet signed the CSR
 
 
Note that the agents CSR includes the agents public key. Now perform the following: 
 

Delete the agents entire SSL directory - including the public / private 

Jira (FACT-1535) facter --list-cache-groups outputs fact names that I cannot resolve with facter

[Nick Walker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1535 
 
 
 
  facter --list-cache-groups outputs fact names that I cannot resolve with facter   
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Walker 
 
 
 
 
 
 
 
 
 
 Trying to use facter fact ttls on the limited info here: https://docs.puppet.com/facter/3.5/release_notes.html#cache-values-easily h1.  Reprodcution {code}[root@agent-181-centos ~]# facter --list-cache-groupspathEC2GCEaugeaskerneloperating systemnetworkingdiskdesktop management interfaceprocessoruptimesshvirtualizationidtimezonefile systemmemoryload_averageXen{code}Okay great I want to know what some of these are so I copy them and run {{facter }}{code}[root@agent-181-centos ~]# facter operating systemoperating => system => [root@agent-181-centos ~]# facter operatingsystemCentOS{code}{code}facter desktop management interfacedesktop => interface => management => [root@agent-181-centos ~]# facter dmi{  bios => {release_date => "12/01/2006",vendor => "innotek GmbH",version => "VirtualBox"  },  board => {manufacturer => "Oracle Corporation",product => "VirtualBox",serial_number => "0"  },  chassis => {type => "Other"  },  manufacturer => "innotek GmbH",  product => {name => "VirtualBox",serial_number => "0",uuid => "50C18B3F-CF21-4079-98F4-F2C6184C5E81"  }}{code}{code}[root@agent-181-centos ~]# facter file systemfile => system => [root@agent-181-centos ~]# facter file[root@agent-181-centos ~]# facter filesystem{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 

Jira (FACT-1535) facter --list-cache-groups outputs fact names that I cannot resolve with facter

[Nick Walker (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Walker created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1535 
 
 
 
  facter --list-cache-groups outputs fact names that I cannot resolve with facter   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/15 6:40 PM 
 
 
 

Labels:
 

 tcse 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Nick Walker 
 
 
 
 
 
 
 
 
 
 
Reprodcution  
 
 
 
 
 
 
[root@agent-181-centos ~]# facter --list-cache-groups 
 
 
 
 
path 
 
 
 
 
EC2 
 
 
 
 
GCE 

Jira (PUP-6761) (SPIKE) Find a workflow for POT file generation

[Geoff Nichols (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6761 
 
 
 
  (SPIKE) Find a workflow for POT file generation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Assignee:
 
 Geoff Nichols 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5908) Implement a PCore MsgPack Serializer

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5908 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Implement a PCore MsgPack Serializer  
 
 
 
 
 
 
 
 
 
 
And it (PA-706) is blocked by PA-621 it seems. Are there any additional things that need to happen (I am thinking for Puppet Server) that is not covered by PA-706? 
I also like to know how to deal with PUP-4742. Create a PA ticket (like PA-706) for what needs to be done for PUP-4742 ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-125) JSON: Splitting function signatures into two places is awkward

[William Hopper (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-125 
 
 
 
  JSON: Splitting function signatures into two places is awkward  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Status:
 
 Ready for  Merge  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 (PUP-5908) Implement a PCore MsgPack Serializer

[Sean McDonald (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean McDonald commented on  PUP-5908 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Implement a PCore MsgPack Serializer  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg The agent team will assist with vendoring the msgpack gem in the agent, PA-706 was created to track that work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6873) functionality for redirecting hiera_xxx calls to lookup, in existing modules

[Lindsey Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lindsey Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6873 
 
 
 
  functionality for redirecting hiera_xxx calls to lookup, in existing modules  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lindsey Smith 
 
 
 
 
 
 
 
 
 
 Given that all modules I use  do  have not changed to use lookup instead of hiera_xxx calls for lookups that are not done via automatic data binding:* I want a way to redirect the hiera_xxx calls to lookup so I am not blocked by switching to lookup because of a module still using hiera_xxx callswhere hiera_xxx is things like hiera_hash, hiera_array, hiera_includeneeds UX work 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2730) Command Processing 2.0

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2730 
 
 
 
  Command Processing 2.0  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

Epic Status:
 
 To Do Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3168) convergence test failiures 11/03/16

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt assigned an issue to Wyatt Alt 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3168 
 
 
 
  convergence test failiures 11/03/16  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Assignee:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3168) convergence test failiures 11/03/16

[Wyatt Alt (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3168 
 
 
 
  convergence test failiures 11/03/16  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2909) Upgrade jdbc (0.4 -> 0.6) in PuppetDB

[Karen Van der Veer (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Karen Van der Veer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2909 
 
 
 
  Upgrade jdbc (0.4 -> 0.6) in PuppetDB  
 
 
 
 
 
 
 
 
 

Change By:
 
 Karen Van der Veer 
 
 
 

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-1534) Acceptance: Facter seg faults on Cisco XR during default file location test

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1534 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Acceptance: Facter seg faults on Cisco XR during default file location test  
 
 
 
 
 
 
 
 
 
 
Did this pass with a previous Facter build/release? If so which was the last you tested? 
Is this the first time this test has been run on Cisco XR? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1534) Acceptance: Facter seg faults on Cisco XR during default file location test

[Michael Smith (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1534 
 
 
 
  Acceptance: Facter seg faults on Cisco XR during default file location test  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 The Cisco XR fails the 'acceptance/tests/options/config_file/ default_filre_location default_file_location .rb' tests with Facter seg faulting.{code}  config file is loaded from default location* Agent ed758rjxyxcsojw.delivery.puppetlabs.net: create config fileed758rjxyxcsojw.delivery.puppetlabs.net (ciscoxr-64-1) 15:12:07$ source /etc/profile; mkdir -p '/etc/puppetlabs/facter'ed758rjxyxcsojw.delivery.puppetlabs.net (ciscoxr-64-1) executed in 0.35 seconds  localhost $ scp /tmp/beaker20161114-1890-1arvuhx ciscoxr-64-1:/etc/puppetlabs/facter/facter.conf {:ignore => }* config file should be loaded automatically and turn DEBUG output oned758rjxyxcsojw.delivery.puppetlabs.net (ciscoxr-64-1) 15:12:07$ source /etc/profile; facter  2016-11-14   23:12:07.946619 INFOpuppetlabs.facter - executed with command line: .  2016-11-14 23:12:07.949131 INFO  leatherman.ruby:137 - ruby loaded from "/opt/puppetlabs/puppet/lib/libruby.so.2.1.0".  sh: line 1:  8338 Segmentation fault  (core dumped) factered758rjxyxcsojw.delivery.puppetlabs.net (ciscoxr-64-1) executed in 5.15 secondsExited: 139Beaker::Host::CommandFailure: Host 'ed758rjxyxcsojw.delivery.puppetlabs.net' exited with 139 running: source /etc/profile; facterLast 10 lines of output were: 2016-11-14 23:12:07.946619 INFO  puppetlabs.facter - executed with command line: . 2016-11-14 23:12:07.949131 INFO  leatherman.ruby:137 - ruby loaded from "/opt/puppetlabs/puppet/lib/libruby.so.2.1.0". sh: line 1:  8338 Segmentation fault  (core dumped) facter/var/lib/jenkins/workspace/platform_puppet-agent_intn-van-sys_suite-manual-facter-master/SLAVE_LABEL/beaker/TEST_TARGET/ciscoxr-64a/facter/acceptance/.bundle/gems/gems/beaker-3.1.0/lib/beaker/host.rb:366/var/lib/jenkins/workspace/platform_puppet-agent_intn-van-sys_suite-manual-facter-master/SLAVE_LABEL/beaker/TEST_TARGET/ciscoxr-64a/facter/acceptance/.bundle/gems/gems/beaker-3.1.0/lib/beaker/dsl/helpers/host_helpers.rb:83/var/lib/jenkins/workspace/platform_puppet-agent_intn-van-sys_suite-manual-facter-master/SLAVE_LABEL/beaker/TEST_TARGET/ciscoxr-64a/facter/acceptance/.bundle/gems/gems/beaker-3.1.0/lib/beaker/shared/host_manager.rb:127/var/lib/jenkins/workspace/platform_puppet-agent_intn-van-sys_suite-manual-facter-master/SLAVE_LABEL/beaker/TEST_TARGET/ciscoxr-64a/facter/acceptance/.bundle/gems/gems/beaker-3.1.0/lib/beaker/dsl/patterns.rb:37/var/lib/jenkins/workspace/platform_puppet-agent_intn-van-sys_suite-manual-facter-master/SLAVE_LABEL/beaker/TEST_TARGET/ciscoxr-64a/facter/acceptance/.bundle/gems/gems/beaker-3.1.0/lib/beaker/dsl/helpers/host_helpers.rb:63/var/lib/jenkins/workspace/platform_puppet-agent_intn-van-sys_suite-manual-facter-master/SLAVE_LABEL/beaker/TEST_TARGET/ciscoxr-64a/facter/acceptance/tests/options/config_file/default_file_location.rb:29

Jira (PUP-6876) Puppet::Settings::IniFile doesn't handle Unicode keys / sections properly - can cause `config set` / `config print` failures

[Glenn Sarti (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6876 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet::Settings::IniFile doesn't handle Unicode keys / sections properly - can cause `config set` / `config print` failures  
 
 
 
 
 
 
 
 
 
 
Ethan Brown You able to help me out with Rel Notes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5908) Implement a PCore MsgPack Serializer

[Craig Gomes (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes commented on  PUP-5908 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Implement a PCore MsgPack Serializer  
 
 
 
 
 
 
 
 
 
 
Happy to hunt down this issue. However, since I'm entirely new to this I don't have much to go on from the ticket. 
What's the gem being added? Is this a new gem or updated? 
Craig W. Gomes | http://www.puppet.com | +1.503.913.7726 Engineering Manager PuppetConf 2016 , 19 - 21 October, San Diego, California *Register to attend or sign up to view the Live Stream * 
On Tue, Nov 15, 2016 at 7:44 AM, Henrik Lindberg (JIRA) < 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6876) Puppet::Settings::IniFile doesn't handle Unicode keys / sections properly - can cause `config set` / `config print` failures

[Kenn Hussey (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-6876 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet::Settings::IniFile doesn't handle Unicode keys / sections properly - can cause `config set` / `config print` failures  
 
 
 
 
 
 
 
 
 
 
Glenn Sarti please fill out the release notes field(s) for this issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6861) [regression] Mount options not idempotent

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6861 
 
 
 
  [regression] Mount options not idempotent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Release Notes Summary:
 
 In Puppet 4.8.0, we added new functionality to the mount provider intended to detect if a mounted filesystem did not match /etc/fstab. Unfortunately, there is not a reliable mechanism for doing this and the detection did not work as intended. It has been removed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6861) [regression] Mount options not idempotent

[Branan Riley (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6861 
 
 
 
  [regression] Mount options not idempotent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

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 (PUP-5993) Possible intermittent test failure in registry_spec.rb

[Ethan Brown (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-5993 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Possible intermittent test failure in registry_spec.rb  
 
 
 
 
 
 
 
 
 
 
Still experiencing intermittent fails as of afd29370 / 11/15/2016 on https://github.com/puppetlabs/puppet/pull/5346 - see https://ci.appveyor.com/project/puppetlabs/puppet/build/4.1.0.3767/job/xyfumeofenyelm3x 
 
 
 
 
 
 
Failures: 
 
 
 
 
  1) Puppet::Util::Windows::Registry#values when reading values should return REG_MULTI_SZ values 
 
 
 
 
 Failure/Error: expect(written).to eq(pair[:value]) 
 
 
 
 
   expected: ["string1", "string2"] 
 
 
 
 
got: ["string1", "string2", "\u7400"] 
 
 
 
 
   (compared using ==) 
 
 
 
 
 # ./spec/integration/util/windows/registry_spec.rb:222:in `block (6 levels) in ' 
 
 
 
 
 # ./spec/integration/util/windows/registry_spec.rb:213:in `block (5 levels) in ' 
 
 
 
 
 # util/rspec_runner:39:in `run' 
 
 
 
 

Jira (PDB-3186) Allow limits in anonymized exports

[Ryan Senior (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Senior created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3186 
 
 
 
  Allow limits in anonymized exports  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/15 8:26 AM 
 
 
 

Labels:
 

 maintenance 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ryan Senior 
 
 
 
 
 
 
 
 
 
 
The current user experience of an anonymized export of a PuppetDB database is pretty bad. We currently export all of the data from PDB instance (anonymizing as we go) and that is returned via HTTP as a tar.gz file. For PDB databases of any decent size, this takes a very long time and can be very large (i.e. 20+ GB). This makes it a time-consuming and difficult process. 
The reason this process takes so long is because we are exporting all reports. There is value in having reports, but there's not a lot of value in having every report for every node. 
We should think through what changes we can make to limit the export/anonymization of reports and still get similar value. The result of this ticket should be a set of tickets with info on what we should change. Some suggestions: 
 

Export only reports that have changes
 

Allow exporting only a given number of nodes worth of data
 

Change the benchmark tool to 

Jira (PDB-3185) Update pdb extensions to handle new maplog

[Rob Browning (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning assigned an issue to Rob Browning 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3185 
 
 
 
  Update pdb extensions to handle new maplog  
 
 
 
 
 
 
 
 
 

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 (PDB-3185) Update pdb extensions to handle new maplog

[Rob Browning (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3185 
 
 
 
  Update pdb extensions to handle new maplog  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/15 8:22 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
Upgrade extensions to the new version of structured logging. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-6538) deprecate hiera_xxx functions (in favour of lookup)

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6538 
 
 
 
  deprecate hiera_xxx functions (in favour of lookup)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6538) deprecate hiera_xxx functions (in favour of lookup)

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6538 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: deprecate hiera_xxx functions (in favour of lookup)  
 
 
 
 
 
 
 
 
 
 
Nicholas Fagerlund can you give us a URL to use 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-6917) the 'site' keyword cannot be used as an attribute name when app_management is on

[Henrik Lindberg (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6917 
 
 
 
  the 'site' keyword cannot be used as an attribute name when app_management is on  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Summary:
 
 the 'site' keyword cannot be used as an attribute name  with  when  app_management is on 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2908) Resolve conflict between i18n and structured-logging

[Rob Browning (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning assigned an issue to Rob Browning 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2908 
 
 
 
  Resolve conflict between i18n and structured-logging  
 
 
 
 
 
 
 
 
 

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 (PDB-3150) [Spike] Investigate and estimate solutions to the "big structure fact" problem

[Rob Browning (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning assigned an issue to Rob Browning 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3150 
 
 
 
  [Spike] Investigate and estimate solutions to the "big structure fact" problem  
 
 
 
 
 
 
 
 
 

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 (PDB-3184) (MAINT) Bump to stockpile 0.0.4

[gepetto-bot (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3184 
 
 
 
  (MAINT) Bump to stockpile 0.0.4  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/11/15 6:54 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
This release includes externalized i18n strings for error messages 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-6917) the 'site' keyword cannot be used as an attribute name with app_management is on

[Kenn Hussey (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6917 
 
 
 
  the 'site' keyword cannot be used as an attribute name with app_management is on  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

Fix Version/s:
 
 PUP 4.8.1 
 
 
 

Fix Version/s:
 
 PUP 4.8.z 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6538) deprecate hiera_xxx functions (in favour of lookup)

[Thomas Hallgren (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6538 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: deprecate hiera_xxx functions (in favour of lookup)  
 
 
 
 
 
 
 
 
 
 
I'm marking this as blocked because I don't know what to put in the deprecation message. A link to the ticket seems to be the only available option at the moment and it's considered a poor UX. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6538) deprecate hiera_xxx functions (in favour of lookup)

[Thomas Hallgren (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6538 
 
 
 
  deprecate hiera_xxx functions (in favour of lookup)  
 
 
 
 
 
 
 
 
 

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.