Jira (PUP-8735) File resource doesn't seem to parse UTF8 filenames when recursively copying directoies

2018-05-15 Thread Glenn Sarti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Sarti commented on  PUP-8735  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: File resource doesn't seem to parse UTF8 filenames when recursively copying directoies   
 

  
 
 
 
 

 
 Bad encoding found!  
 
 
 
 
 [10] pry(#)> whereami  
 
 
    
 
 
 Frame number: 0/62  
 
 
    
 
 
 From: C:/Source/tmp/utf8-repro/.bundle/windows/ruby/2.3.0/gems/puppet-5.5.1-x64-mingw32/lib/puppet/file_serving/fileset.rb @ line 127 Puppet::FileServing::Fileset::FileSetEntry#children:  
 
 
    
 
 
 122: def children  
 
 
 123:   return [] unless directory?  
 
 
 124: require 'pry'; binding.pry  
 
 
 125:   Dir.entries(path).  
 
 
 126: reject { |child| ignore?(child) }.  
 
 
  => 127: collect { |child| down_level(child) }  
 
 
 128: end
  
 

Jira (PUP-8735) File resource doesn't seem to parse UTF8 filenames when recursively copying directoies

2018-05-15 Thread Glenn Sarti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Sarti commented on  PUP-8735  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: File resource doesn't seem to parse UTF8 filenames when recursively copying directoies   
 

  
 
 
 
 

 
 FileSet has the munging  
 
 
 
 
 From: C:/Source/tmp/utf8-repro/.bundle/windows/ruby/2.3.0/gems/puppet-5.5.1-x64-mingw32/lib/puppet/file_serving/fileset.rb @ line 153 Puppet::FileServing::Fileset#perform_recursion:  
 
 
    
 
 
 146:   def perform_recursion  
 
 
 147: current_dirs = [FileSetEntry.new(0, @path, @ignore, @stat_method)]  
 
 
 148: require 'pry'; binding.pry  
 
 
 149: result = []  
 
 
 150:  
 
 
 151: while entry = current_dirs.shift  
 
 
 152:   if continue_recursion_at?(entry.depth + 1)  
 
 
  => 153: entry.children.each do |child|  
 
 
 154:   result << child.path  
 
 
 155:   current_dirs << child  
 
 
 156:  

Jira (PUP-5491) The "client_data" Directory Permissions Incorrect After Installation

2018-05-15 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-5491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The "client_data" Directory Permissions Incorrect After Installation   
 

  
 
 
 
 

 
 FYI I can repro this by installing puppet-agent as a manual service. Run puppet config set server  --section main. Then run puppet agent -t from an admin elevated cmd.exe shell.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8735) File resource doesn't seem to parse UTF8 filenames when recursively copying directoies

2018-05-15 Thread Glenn Sarti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Sarti commented on  PUP-8735  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: File resource doesn't seem to parse UTF8 filenames when recursively copying directoies   
 

  
 
 
 
 

 
 Looks like the resource generator is not round tripping the filename correctly  
 
 
 
 
 ...  
 
 
   @parameters=  
 
 
  {:path=>#, @value="c:/install/test2/Testing-words\xE9">,  
 
 
   :provider=>#, @value=:windows>,  
 
 
   :replace=>#, @value=true>,  
 
 
   :backup=>#, @value="puppet">,  
 
 
   :links=>#, @value=:manage>,  
 
 
   :purge=>#, @value=false>,  
 
 
   :sourceselect=>#, @value=:first>,  
 
 
   :show_diff=>#, @value=true>,  
 
 
   :validate_replacement=>#, @value="%">,  
 
 
   :checksum=>#, @value=:md5>,  
 
 
   :source_permissions=>#, @value=:ignore>,  
  

Jira (PUP-8735) File resource doesn't seem to parse UTF8 filenames when recursively copying directoies

2018-05-15 Thread Glenn Sarti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Sarti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8735  
 
 
  File resource doesn't seem to parse UTF8 filenames when recursively copying directoies   
 

  
 
 
 
 

 
Change By: 
 Glenn Sarti  
 
 
Attachment: 
 debug-out.txt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8735) File resource doesn't seem to parse UTF8 filenames when recursively copying directoies

2018-05-15 Thread Glenn Sarti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Sarti commented on  PUP-8735  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: File resource doesn't seem to parse UTF8 filenames when recursively copying directoies   
 

  
 
 
 
 

 
 Full trace dump attached  debug-out.txt   
 
 
 
 
 ...  
 
 
 C:/Source/tmp/utf8-repro/.bundle/windows/ruby/2.3.0/gems/puppet-5.5.1-x64-mingw32/lib/puppet/application.rb:375:in `run'  
 
 
 C:/Source/tmp/utf8-repro/.bundle/windows/ruby/2.3.0/gems/puppet-5.5.1-x64-mingw32/lib/puppet/util/command_line.rb:137:in `run'  
 
 
 C:/Source/tmp/utf8-repro/.bundle/windows/ruby/2.3.0/gems/puppet-5.5.1-x64-mingw32/lib/puppet/util/command_line.rb:73:in `execute'  
 
 
 C:/Source/tmp/utf8-repro/.bundle/windows/ruby/2.3.0/gems/puppet-5.5.1-x64-mingw32/bin/puppet:5:in `'  
 
 
 C:/Source/tmp/utf8-repro/.bundle/windows/ruby/2.3.0/bin/puppet:23:in `load'  
 
 
 C:/Source/tmp/utf8-repro/.bundle/windows/ruby/2.3.0/bin/puppet:23:in `'  
 
 
 Wrapped exception:  
 
 
 invalid byte sequence in UTF-8  
 
 
 C:/Source/tmp/utf8-repro/.bundle/windows/ruby/2.3.0/gems/puppet-5.5.1-x64-mingw32/lib/puppet/util.rb:361:in `sub!'  
 
 
 C:/Source/tmp/utf8-repro/.bundle/windows/ruby/2.3.0/gems/puppet-5.5.1-x64-mingw32/lib/puppet/util.rb:361:in `uri_to_path'  
 
 

Jira (PUP-8735) File resource doesn't seem to parse UTF8 filenames when recursively copying directoies

2018-05-15 Thread Glenn Sarti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Glenn Sarti created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8735  
 
 
  File resource doesn't seem to parse UTF8 filenames when recursively copying directoies   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.5.1  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/15 9:31 PM  
 
 
Environment: 
 Windows 10 - 1803 Puppet Agent 5.3.3 and Puppet as a gem 5.5.1  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Glenn Sarti  
 

  
 
 
 
 

 
 Puppet Version: 5.5.1 (Win x64) Puppet Server Version: N/A OS Name/Version: Windows 10 - 1803 Desired Behavior: Given a manifest saved as UTF8  
 
 
 
 
 file { "c:\\install\\test\\Testing-wordsé":  
 
 
   ensure  => file,  
 
 
   content => 'Testing é',  
 
 
 } ->  
 
 
    
  

Jira (PUP-8734) Build program in Marketo

2018-05-15 Thread Claire Papas (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claire Papas created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8734  
 
 
  Build program in Marketo   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Allison Rick  
 
 
Created: 
 2018/05/15 4:54 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Claire Papas  
 

  
 
 
 
 

 
 Registration page built - https://app-sjh.marketo.com/#LP10955A1LA1 Can you QA? Just need this to get it on Puppet.com tonight  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 
   

Jira (FACT-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms

2018-05-15 Thread Casey Williams (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Williams commented on  FACT-620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms   
 

  
 
 
 
 

 
 Closing – per Eric Sorenson's reluctance, we feel the benefits of consistency here wouldn't outweigh the breakage across existing puppet code that this would cause.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-1688) When applying a mode of 0466 on Windows, a mode of 0666 is applied instead

2018-05-15 Thread Jayant Sane (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jayant Sane commented on  PUP-1688  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: When applying a mode of 0466 on Windows, a mode of 0666 is applied instead   
 

  
 
 
 
 

 
 Disregard if this is off but based on my limited review qualified take is - this looks ok particularly for this mode mapping. I would be less concerned with owner ending up with a write access (when group/others have that access).   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1142) Facter FQDN resolution is incorrect on Windows

2018-05-15 Thread Casey Williams (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1142  
 
 
  Facter FQDN resolution is incorrect on Windows   
 

  
 
 
 
 

 
Change By: 
 Casey Williams  
 
 
Sprint: 
 Platform OS Ready for Eng.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1790) facter should compute the correct processor facts for arm64 Linux machines

2018-05-15 Thread Scott Garman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Garman commented on  FACT-1790  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: facter should compute the correct processor facts for arm64 Linux machines   
 

  
 
 
 
 

 
 Richard Henwood This would involve some work in https://github.com/puppetlabs/facter/blob/master/lib/src/facts/linux/processor_resolver.cc to add a method for something along the lines of processor_resolver::add_arm_cpu_data, which would query the information by parsing output from dmidecode.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1501) timezone contains wrong value

2018-05-15 Thread Casey Williams (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Williams updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1501  
 
 
  timezone contains wrong value   
 

  
 
 
 
 

 
Change By: 
 Casey Williams  
 
 
Labels: 
 needs_repro timezo triaged windows  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDB-3922) Build from source instructions don't work outside our network

2018-05-15 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3922  
 
 
  Build from source instructions don't work outside our network   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Component/s: 
 DOCS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-4039) package resource doesn't find new packages in yum repo

2018-05-15 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-4039  
 
 
  package resource doesn't find new packages in yum repo   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Sprint: 
 Client 2016-05-04, Platform OS  Community PR  Kanban  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-6531) puppet service provider recognition on Ubuntu can be improved

2018-05-15 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6531  
 
 
  puppet service provider recognition on Ubuntu can be improved   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Sprint: 
 Platform OS  Community PR  Kanban  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1764) Error message with zpool_vesion fact when zfs service is installed bt not running

2018-05-15 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1764  
 
 
  Error message with zpool_vesion fact when zfs service is installed bt not running   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Sprint: 
 Platform OS  Community PR  Kanban  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-3631) NIM provider uses a regex that is too restrictive when parsing RPM release tags

2018-05-15 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3631  
 
 
  NIM provider uses a regex that is too restrictive when parsing RPM release tags   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Labels: 
 aix  package  triaged  type_package  type_and_provider  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-3611) Implement install_options for nim package provider

2018-05-15 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3611  
 
 
  Implement install_options for nim package provider   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Labels: 
 aix  package  triaged  type_package  type_and_provider  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1843) Make prtdiag timeout configurable on Solaris

2018-05-15 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1843  
 
 
  Make prtdiag timeout configurable on Solaris   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Sprint: 
 Platform OS Ready for Eng.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1843) Make prtdiag timeout configurable on Solaris

2018-05-15 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1843  
 
 
  Make prtdiag timeout configurable on Solaris   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Sprint: 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1741) Ensure facts are reported correctly on EL 7 (AArch64)

2018-05-15 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1741  
 
 
  Ensure facts are reported correctly on EL 7 (AArch64)   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Sprint: 
 Platform OS Ready for Eng.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1741) Ensure facts are reported correctly on EL 7 (AArch64)

2018-05-15 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1741  
 
 
  Ensure facts are reported correctly on EL 7 (AArch64)   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Sprint: 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1790) facter should compute the correct processor facts for arm64 Linux machines

2018-05-15 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1790  
 
 
  facter should compute the correct processor facts for arm64 Linux machines   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Sprint: 
 Platform OS Grooming/Triage  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-6510) selmodule provider should only list modules once

2018-05-15 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6510  
 
 
  selmodule provider should only list modules once   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Sprint: 
 Platform OS  Grooming/Triage  Ready for Eng.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-3263) Architecture Parameter for Package Resource

2018-05-15 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3263  
 
 
  Architecture Parameter for Package Resource   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Labels: 
 customer linux  needs_repro  package triaged type_and_provider  yum  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-3263) Architecture Parameter for Package Resource

2018-05-15 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3263  
 
 
  Architecture Parameter for Package Resource   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Sprint: 
 Platform OS Grooming/Triage  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1762) valid networking facts in 2.x get ignored in 3.x

2018-05-15 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1762  
 
 
  valid networking facts in 2.x get ignored in 3.x   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Sprint: 
 Platform OS Grooming/Triage  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1762) valid networking facts in 2.x get ignored in 3.x

2018-05-15 Thread Larissa Lane (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Larissa Lane commented on  FACT-1762  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: valid networking facts in 2.x get ignored in 3.x   
 

  
 
 
 
 

 
 Garrett Guillotte We might need some documentation for this  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1762) valid networking facts in 2.x get ignored in 3.x

2018-05-15 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1762  
 
 
  valid networking facts in 2.x get ignored in 3.x   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Labels: 
 breaking linux networking triaged  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1732) Facter core dump on large integers

2018-05-15 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1732  
 
 
  Facter core dump on large integers   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Sprint: 
 Platform OS  Grooming/Triage  Ready for Eng.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1732) Facter core dump on large integers

2018-05-15 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1732  
 
 
  Facter core dump on large integers   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Fix Version/s: 
 FACT 4.0.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDOC-249) Yardoc "Extra Files" Link doesn't display

2018-05-15 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam commented on  PDOC-249  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Yardoc "Extra Files" Link doesn't display   
 

  
 
 
 
 

 
 this conditional is broken. This may have been true in older versions of YARD, but the Registry now never contains files: https://github.com/puppetlabs/puppet-strings/blob/master/lib/puppet-strings/yard/templates/default/layout/html/setup.rb#L128   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDOC-249) Yardoc "Extra Files" Link doesn't display

2018-05-15 Thread David Hollinger (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Hollinger created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-249  
 
 
  Yardoc "Extra Files" Link doesn't display   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Screen Shot 2018-05-15 at 2.50.48 PM.png, Screen Shot 2018-05-15 at 2.51.10 PM.png, Screen Shot 2018-05-15 at 3.31.29 PM.png  
 
 
Created: 
 2018/05/15 1:31 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 David Hollinger  
 

  
 
 
 
 

 
 When using the yardoc Extra Files feature via .yardopts:  
 
 
 
 
 --markup markdown  
 
 
 --output-dir public  
 
 
 -  
 
 
 CHANGELOG.md  
 
 
 docs/Overview.md  
 
 
 
  Puppet Strings will still add the "extra files" to the 

Jira (BOLT-392) Application Deployment Plan

2018-05-15 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman assigned an issue to Alex Dreyer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-392  
 
 
  Application Deployment Plan   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Assignee: 
 Lucy Wyman Alex Dreyer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-224) After running a plan, provide an easy way to re-invoke individual plan steps

2018-05-15 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi commented on  BOLT-224  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: After running a plan, provide an easy way to re-invoke individual plan steps   
 

  
 
 
 
 

 
 Reid Vandewiele do you have a real world example of this issue?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-521) I want to escalate with a non-sudo command

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-521  
 
 
  I want to escalate with a non-sudo command   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/15 11:49 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Alex Dreyer  
 

  
 
 
 
 

 
 Some users use a command other than sudo to escalate privileges. Bolt should support running a different command for escalation  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   

Jira (BOLT-299) Run As

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-299  
 
 
  Run As   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Epic Status: 
 To Do Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8733) File type redefined when required in code

2018-05-15 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8733  
 
 
  File type redefined when required in code   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Affects Version/s: 
 SERVER 0.2.1  
 
 
Affects Version/s: 
 PUP 5.5.1  
 
 
Key: 
 SERVER PUP - 64 8733  
 
 
Project: 
 Puppet  Server  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PUP-8548) File isn't synced to disk

2018-05-15 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley commented on  PUP-8548  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: File isn't synced to disk   
 

  
 
 
 
 

 
 Doing a bit of googling I see several old and closed issues against Docker related to filesystem issues (mostly at build time) - if there was some sort of FS issue under the hood in Docker, it could definitely also affect puppet runs. Since you can't reproduce this in your current set of deployments, I'm going to go ahead and close for now. If you can come up with any new data that makes it look like a Puppet issue again, feel free to reopen.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-297) Plan Output

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-297  
 
 
  Plan Output   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Epic Status: 
 To Do Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-148) Fully implement task spec

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-148  
 
 
  Fully implement task spec   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Epic Status: 
 To Do Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-321) Bolt stdlib

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-321  
 
 
  Bolt stdlib   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Epic Status: 
 In Progress Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-219) Transport API

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer commented on  BOLT-219  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Transport API   
 

  
 
 
 
 

 
 There will be another round of transport API work to capture configuring new transports that ship outside of bolt.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-219) Transport API

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-219  
 
 
  Transport API   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Epic Status: 
 To Do Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-519) Bolt should send a Bolt user agent header to orchestrator

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-519  
 
 
  Bolt should send a Bolt user agent header to orchestrator   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Sprint: 
 Bolt  Ready for Grooming  Kanban  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-488) I would like to know how often subcommands in bolt are run

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-488  
 
 
  I would like to know how often subcommands in bolt are run   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 Bolt should send what subcommand is being used to google analytics. This command should be sent from a separate thread from CLI before the action is started.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-488) I would like to know how often subcommands in bolt are run

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-488  
 
 
  I would like to know how often subcommands in bolt are run   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 Bolt should send what subcommand is being used to google analytics.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-488) I would like to know how often subcommands in bolt are run

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-488  
 
 
  I would like to know how often subcommands in bolt are run   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Sprint: 
 Bolt  Ready for Grooming  Kanban  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-492) turn off analytics

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-492  
 
 
  turn off analytics   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Summary: 
 turn off analytics  support in bolt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-492) analytics support in bolt

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-492  
 
 
  analytics support in bolt   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Summary: 
 As a bolt user I would like to turn off  analytics  support in bolt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-492) As a bolt user I would like to turn off analytics

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-492  
 
 
  As a bolt user I would like to turn off analytics   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Issue Type: 
 Story New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-380) Support ed25519 out-of-the-box

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer assigned an issue to Nick Lewis  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-380  
 
 
  Support ed25519 out-of-the-box   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Assignee: 
 Nick Lewis  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-518) Facter task does not correctly detect Ubuntu OS family

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer assigned an issue to Cas Donoghue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-518  
 
 
  Facter task does not correctly detect Ubuntu OS family
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Assignee: 
 Cas Donoghue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-518) Facter task does not correctly detect Ubuntu OS family

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer commented on  BOLT-518  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Facter task does not correctly detect Ubuntu OS family
 

  
 
 
 
 

 
 We should fix this to make sure the fact task works well in the hands on lab without breaking any other cases.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-135) I want to execute different versions of the task file on different platforms

2018-05-15 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis assigned an issue to Alex Dreyer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-135  
 
 
  I want to execute different versions of the task file on different platforms   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
Assignee: 
 Nick Lewis Alex Dreyer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8588) Support multiple implementations when loading tasks

2018-05-15 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis assigned an issue to Alex Dreyer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8588  
 
 
  Support multiple implementations when loading tasks   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
Assignee: 
 Nick Lewis Alex Dreyer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-486) Bolt plan help mentions using --query

2018-05-15 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-486  
 
 
  Bolt plan help mentions using --query   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDOC-246) Puppet Strings for puppetlabs-postgresql

2018-05-15 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-246  
 
 
  Puppet Strings for puppetlabs-postgresql   
 

  
 
 
 
 

 
Change By: 
 Eric Putnam  
 
 
Summary: 
 Puppet Strings for puppetlabs-postgresql  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDOC-248) Puppet Strings for puppetlabs-tomcat

2018-05-15 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-248  
 
 
  Puppet Strings for puppetlabs-tomcat   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/15 11:00 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Putnam  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PDOC-247) Puppet Strings for puppetlabs-apache

2018-05-15 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-247  
 
 
  Puppet Strings for puppetlabs-apache   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/15 11:00 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Putnam  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PDOC-245) Puppet Strings for puppetlabs-ntp

2018-05-15 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-245  
 
 
  Puppet Strings for puppetlabs-ntp   
 

  
 
 
 
 

 
Change By: 
 Eric Putnam  
 
 
Summary: 
 Puppet Strings for puppetlabs-ntp  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDOC-244) Puppet Strings for puppetlabs-stdlib

2018-05-15 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-244  
 
 
  Puppet Strings for puppetlabs-stdlib   
 

  
 
 
 
 

 
Change By: 
 Eric Putnam  
 
 
Summary: 
 Puppet Strings for puppetlabs-stdlib  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDOC-244) puppetlabs-stdlib

2018-05-15 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-244  
 
 
  puppetlabs-stdlib   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/15 10:58 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Putnam  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PDOC-245) puppetlabs-ntp

2018-05-15 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-245  
 
 
  puppetlabs-ntp   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/15 10:58 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Putnam  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PDOC-246) puppetlabs-postgresql

2018-05-15 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-246  
 
 
  puppetlabs-postgresql   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/15 10:58 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Putnam  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PUP-7600) Deprecate built-in LDAP Node Terminus

2018-05-15 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland assigned an issue to Kris Bosland  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7600  
 
 
  Deprecate built-in LDAP Node Terminus   
 

  
 
 
 
 

 
Change By: 
 Kris Bosland  
 
 
Assignee: 
 Kris Bosland  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8732) Investigate if Puppet Device pluginsync can be limited to remote modules

2018-05-15 Thread Mike Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Smith commented on  PUP-8732  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Investigate if Puppet Device pluginsync can be limited to remote modules   
 

  
 
 
 
 

 
 Testing now with SE demo env and first run is syncing all types and thus taking upwards of 15+ minutes.  Appears to run ~2/sec with PE in Slice and the network testing 6509  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8732) Investigate if Puppet Device pluginsync can be limited to remote modules

2018-05-15 Thread Rick Sherman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Sherman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8732  
 
 
  Investigate if Puppet Device pluginsync can be limited to remote modules   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/15 9:32 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rick Sherman  
 

  
 
 
 
 

 
 Currently Puppet Device pluginsync processes all items.  We should see if this can be limited to items that relate to Puppet Device. This would benefit uses in pluginsync time and duplication of files, as a cache is maintained for  each node Puppet Device manages.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (PDB-3924) Avoid temp file flood during fact path gc

2018-05-15 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3924  
 
 
  Avoid temp file flood during fact path gc   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/15 9:31 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rob Browning  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (BOLT-494) Document how to opt-out of analytics

2018-05-15 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer commented on  BOLT-494  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Document how to opt-out of analytics   
 

  
 
 
 
 

 
 Ryan and Yasmin have reviewed this.  I've reached out to legal to start a conversation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDB-3923) Avoid set-returning functions in case in delete-unused-fact-paths

2018-05-15 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3923  
 
 
  Avoid set-returning functions in case in delete-unused-fact-paths   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Summary: 
 Rewrite  Avoid set-returning functions in case in delete-unused-fact-paths  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDB-3923) Avoid set-returning functions in case in delete-unused-fact-paths

2018-05-15 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3923  
 
 
  Avoid set-returning functions in case in delete-unused-fact-paths   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 

  
 
 
 
 

 
 With pg 10 that is right out.   We'll probably want to rewrite it as a lateral join.
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDB-3923) Rewrite

2018-05-15 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3923  
 
 
  Rewrite
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/15 9:01 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rob Browning  
 

  
 
 
 
 

 
 With pg 10 that is right out.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 
   

Jira (PUP-7918) puppet fails to change user group membership if directory group names have spaces

2018-05-15 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7918  
 
 
  puppet fails to change user group membership if directory group names have spaces   
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
CS Impact: 
 Our largest customers are going to most likely have existing AD implementations and it is not uncommon at all for there to be duplication of local groups and AD groups.  It is also not uncommon for AD entities to have spaces in their names.  We need to work correctly in that environment.  
 
 
CS Severity: 
 3 - Serious  
 
 
CS Business Value: 
 4 - $  
 
 
CS Frequency: 
 2 - 5-25% of Customers  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

 

Jira (PUP-8664) rpm package provider is too specific

2018-05-15 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
CS Priority: 
 Needs Priority Normal  
 
 
CS Impact: 
 The rpm provider should allow for a single run to ensure absent one package and ensure present another.  The fact this fails in any case is a bug worth fixing.  There is already a PR attached.  
 
 
CS Severity: 
 3 - Serious  
 
 
CS Business Value: 
 3 -   
 
 
CS Frequency: 
 1 - 1-5% of Customers  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
  

Jira (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace

2018-05-15 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-4242  
 
 
  Add deprecation warnings for manifests declaring things in wrong namespace   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Kris Bosland  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-392) Application Deployment Plan

2018-05-15 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman assigned an issue to Lucy Wyman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-392  
 
 
  Application Deployment Plan   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Assignee: 
 Alex Dreyer Lucy Wyman  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8664) rpm package provider is too specific

2018-05-15 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
Labels: 
 cs_pr_review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8604) Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet

2018-05-15 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Thomas Hallgren  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8604  
 
 
  Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Henrik Lindberg Thomas Hallgren  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8325) Trusted facts can't be structured data

2018-05-15 Thread Adam Bottchen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Bottchen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8325  
 
 
  Trusted facts can't be structured data   
 

  
 
 
 
 

 
Change By: 
 Adam Bottchen  
 
 
CS Priority: 
 Needs Priority Normal  
 
 
CS Impact: 
 We believe ASN.1 supports this, and it is logical for customers to expect it to work since we have structured facts in general.  It is a surprise when it gets converted to a string and could potentially lead to difficult to diagnose problems.  
 
 
CS Severity: 
 4 - Major  
 
 
CS Business Value: 
 4 - $  
 
 
CS Frequency: 
 1 - 1-5% of Customers  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  

Jira (PUP-8731) Update specification of "parameter scope" to cover when types are asserted

2018-05-15 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8731  
 
 
  Update specification of "parameter scope" to cover when types are asserted   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/15 7:40 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Henrik Lindberg  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PUP-8728) A parameter that does not pass type validation can cause catalog compilation failure if used in the default expression of another parameter

2018-05-15 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg assigned an issue to Thomas Hallgren  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8728  
 
 
  A parameter that does not pass type validation can cause catalog compilation failure if used in the default _expression_ of another parameter
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Assignee: 
 Thomas Hallgren  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8728) A parameter that does not pass type validation can cause catalog compilation failure if used in the default expression of another parameter

2018-05-15 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-8728  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: A parameter that does not pass type validation can cause catalog compilation failure if used in the default _expression_ of another parameter
 

  
 
 
 
 

 
 I targeted Puppet 6.0.0 for this since there is a small chance that it may break someone's code.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8728) A parameter that does not pass type validation can cause catalog compilation failure if used in the default expression of another parameter

2018-05-15 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8728  
 
 
  A parameter that does not pass type validation can cause catalog compilation failure if used in the default _expression_ of another parameter
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Fix Version/s: 
 PUP 6.0.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8728) A parameter that does not pass type validation can cause catalog compilation failure if used in the default expression of another parameter

2018-05-15 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-8728  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: A parameter that does not pass type validation can cause catalog compilation failure if used in the default _expression_ of another parameter
 

  
 
 
 
 

 
 Thomas Hallgren Any thoughts on multiple dispatch? What if we introduced that in the puppet language? How would that work, say you have a first parameter Integer[10] $x, String $y = foo($x), and a second Integer[20] $x, Integer $y = foo($y) - here you cannot assert $x until you have established that it is the second signature that is going to be used (because the default _expression_ returned an Integer). We would get around that problem by specifying that values returned by default value expressions are not involved in the selection of signature - which I think is quite reasonable.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8730) Yumrepo Parameters: report_instanceid and fastestmirror_enabled

2018-05-15 Thread Mike Peachey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Peachey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8730  
 
 
  Yumrepo Parameters: report_instanceid and fastestmirror_enabled   
 

  
 
 
 
 

 
Change By: 
 Mike Peachey  
 

  
 
 
 
 

 
 *Puppet Version: 5.5.1* **  *OS Name/Version: Amazon Linux**Desired Behavior:*{{report_instanceid and fastestmirror_enabled parameters can be set as parameters to a Yumrepo definition. ** }}*Actual Behavior:**{{Error: no parameter named 'fastestmirror_enabled'}}**{{Error: no parameter named 'report_instanceid'}}* *CAVEAT:*report_instanceid is valid and very immediately desirable; however fastestmirror_enabled is defined in Amazon Linux, and supported by Chef already, but I am not convinced it does anything. I haven't yet found any applicable yum or fastestmirror plugin source code that consumes this parameter.**   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PUP-8730) Yumrepo Parameters: report_instanceid and fastestmirror_enabled

2018-05-15 Thread Mike Peachey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Peachey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8730  
 
 
  Yumrepo Parameters: report_instanceid and fastestmirror_enabled   
 

  
 
 
 
 

 
Change By: 
 Mike Peachey  
 

  
 
 
 
 

 
 *Puppet Version: 5.5.1* *OS Name/Version: Amazon Linux**Desired Behavior:*{{report_instanceid and fastestmirror_enabled parameters can be set as parameters to a Yumrepo definition.}}*Actual Behavior:**{{Error: no parameter named 'fastestmirror_enabled'}}**{{Error: no parameter named 'report_instanceid'}}* *CAVEAT:*report_instanceid is valid and very immediately desirable; however fastestmirror_enabled is defined in Amazon Linux, and supported by Chef already, but I am not convinced it does anything. I haven't yet found any applicable yum or fastestmirror plugin source code that consumes this parameter. **    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (PUP-8730) Yumrepo Parameters: report_instanceid and fastestmirror_enabled

2018-05-15 Thread Mike Peachey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Peachey commented on  PUP-8730  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Yumrepo Parameters: report_instanceid and fastestmirror_enabled   
 

  
 
 
 
 

 
 https://github.com/puppetlabs/puppet/pull/6834  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8730) Yumrepo Parameters: report_instanceid and fastestmirror_enabled

2018-05-15 Thread Mike Peachey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Peachey created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8730  
 
 
  Yumrepo Parameters: report_instanceid and fastestmirror_enabled   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Affects Versions: 
 PUP 5.5.1  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Types and Providers  
 
 
Created: 
 2018/05/15 6:27 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Mike Peachey  
 

  
 
 
 
 

 
 Puppet Version: 5.5.1** OS Name/Version: Amazon Linux Desired Behavior: report_instanceid and fastestmirror_enabled parameters can be set as parameters to a Yumrepo definition.** Actual Behavior: Error: no parameter named 'fastestmirror_enabled' Error: no parameter named 'report_instanceid'   CAVEAT: report_instanceid is valid and very immediately desirable; however fastestmirror_enabled is defined in Amazon Linux, and supported by Chef already, but I am not convinced it does anything. I haven't yet found any applicable yum or fastestmirror plugin source code that consumes this parameter.**    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
  

Jira (PUP-8728) A parameter that does not pass type validation can cause catalog compilation failure if used in the default expression of another parameter

2018-05-15 Thread Thomas Hallgren (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Hallgren commented on  PUP-8728  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: A parameter that does not pass type validation can cause catalog compilation failure if used in the default _expression_ of another parameter
 

  
 
 
 
 

 
 I would have assumed that this already happened but apparently all parameter values are first calculated and then type checked. That's clearly a bug. $test should never be able to hold the value of 63. The fix is probably trivial. The code needs to check each individual parameter instead of checking the full Tuple at the end (probably means that APL assignments must be checked individually as well).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8728) A parameter that does not pass type validation can cause catalog compilation failure if used in the default expression of another parameter

2018-05-15 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-8728  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: A parameter that does not pass type validation can cause catalog compilation failure if used in the default _expression_ of another parameter
 

  
 
 
 
 

 
 It would be nice if arguments were validated before they get used in a default value _expression_. Ping Thomas Hallgren - do you think this is difficult to achieve? For puppet functions it should work since they are single dispatch, but I imagine this being very difficult for multiple dispatch 4.x functions (where on the other hand, you would need to do the default value evaluation inside the body of a function method.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8548) File isn't synced to disk

2018-05-15 Thread Matthias Baur (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthias Baur commented on  PUP-8548  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: File isn't synced to disk   
 

  
 
 
 
 

 
 Not exactly, '/' is on one partition on the Docker Host and in the Docker Container. We did a lot of changes on our CI lately including changing the Docker storage driver from aufs to overlay2, switching from Jenkins to Gitlab CI, ... After all those changes we haven't seem the error in the last couple of weeks.   Still, the issue seems kind of odd.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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