Jira (PUP-8199) Parameters in Task metadata should not collide with metadata keys

2017-11-28 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8199 
 
 
 
  Parameters in Task metadata should not collide with metadata keys  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8211) Allow managehome to modify home directory for existing users

2017-11-28 Thread Simon Beirnaert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Simon Beirnaert commented on  PUP-8211 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow managehome to modify home directory for existing users  
 
 
 
 
 
 
 
 
 
 
I'm the guy who actually put this forward via support.puppet.com. 
Whether or not you fix this: please update the current docs with this information. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3807) 'puppet config print' should sort the output

2017-11-28 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3807 
 
 
 
  'puppet config print' should sort the output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3807) 'puppet config print' should sort the output

2017-11-28 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3807 
 
 
 
  'puppet config print' should sort the output  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3807) 'puppet config print' should sort the output

2017-11-28 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-3807 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 'puppet config print' should sort the output  
 
 
 
 
 
 
 
 
 
 
Merged to 5.3.x at 43b4de8. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-44) Display human-readable results from running a task

2017-11-28 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-44 
 
 
 
  Display human-readable results from running a task  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Labels:
 
 docs_reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-44) Display human-readable results from running a task

2017-11-28 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette commented on  BOLT-44 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Display human-readable results from running a task  
 
 
 
 
 
 
 
 
 
 
Added new feature release note. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-4065) errors/warnings in environment.conf should not be duplicated

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-4065 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: errors/warnings in environment.conf should not be duplicated  
 
 
 
 
 
 
 
 
 
 
This error comes from, and is trivial to fix: 
 
 
 
 
 
 
  Puppet.warning(_(" 
 
 
 
 
Invalid settings in environment.conf at '%{path_to_conf_file}'. The following unknown setting(s) are being ignored: %{ignored_settings}") % { path_to_conf_file: path_to_conf_file, ignored_settings: extraneous_settings.join(', ') })
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-4085) Windows Agents should report User in the event log

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4085 
 
 
 
  Windows Agents should report User in the event log  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Labels:
 
 beginner windows 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-4065) errors/warnings in environment.conf should not be duplicated

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4065 
 
 
 
  errors/warnings in environment.conf should not be duplicated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Labels:
 
 beginner this_issue_is_bad_and_you_should_feel_bad 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-72) Don't invoke new powershell instances

2017-11-28 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette commented on  BOLT-72 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Don't invoke new powershell instances  
 
 
 
 
 
 
 
 
 
 
added new feature release note. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-72) Don't invoke new powershell instances

2017-11-28 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-72 
 
 
 
  Don't invoke new powershell instances  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Labels:
 
 docs_reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-2890) Puppet Resource Interface errors in unsupported environments

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2890 
 
 
 
  Puppet Resource Interface errors in unsupported environments  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 5.y 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-2890) Puppet Resource Interface errors in unsupported environments

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2890 
 
 
 
  Puppet Resource Interface errors in unsupported environments  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Team:
 
 Platform Core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-2890) Puppet Resource Interface errors in unsupported environments

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-2890 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet Resource Interface errors in unsupported environments  
 
 
 
 
 
 
 
 
 
 
ping Rick Sherman, this is an issue when trying to collect instances of the interface type. The issue occurs because the provider doesn't implement the instances method: 
 
 
 
 
 
 
def self.instances 
 
 
 
 
  [] 
 
 
 
 
end
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-4442) The error message associated with a file resource that requires a non-existent directory is misleading.

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-4442 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The error message associated with a file resource that requires a non-existent directory is misleading.  
 
 
 
 
 
 
 
 
 
 
The ensure behavior was fixed in https://github.com/puppetlabs/puppet/commit/ca60ff8e4c00139522cdb570f8d4c3bb3e2aa847 (in 4.4.2). However, puppet needs to rescue ENOENT if mkdir fails, and generate a meaningful error message, and the message should reference the parent directory, not the lock file. The current behavior is still confusing: 
 
 
 
 
 
 
$ bundle exec puppet apply -e 'file { "/tmp/foo/bar/baz": ensure => file, content => "hi" }' 
 
 
 
 
Notice: Compiled catalog for XXX in environment production in 0.02 seconds 
 
 
 
 
Error: Could not set 'file' on ensure: No such file or directory @ dir_s_mkdir - /tmp/foo/bar/baz20171128-80116-1rs9wks.lock at line 1 
 
 
 
 
Error: Could not set 'file' on ensure: No such file or directory @ dir_s_mkdir - /tmp/foo/bar/baz20171128-80116-1rs9wks.lock at line 1 
 
 
 
 
Wrapped exception: 
 
 
 
 
No such file or directory @ dir_s_mkdir - /tmp/foo/bar/baz20171128-80116-1rs9wks.lock 
 
 
 
 
Error: /Stage[main]/Main/File[/tmp/foo/bar/baz]/ensure: change from 'absent' to 'file' failed: Could not set 'file' on ensure: No such file or directory @ dir_s_mkdir - /tmp/foo/bar/baz20171128-80116-1rs9wks.lock at line 1 
 
 
 
 
Notice: Applied catalog in 0.01 seconds
 
 
  

Jira (PUP-4442) The error message associated with a file resource that requires a non-existent directory is misleading.

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4442 
 
 
 
  The error message associated with a file resource that requires a non-existent directory is misleading.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Labels:
 
 beginner 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-225) Support SCP for file transfer

2017-11-28 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette commented on  BOLT-225 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support SCP for file transfer  
 
 
 
 
 
 
 
 
 
 
New feature release note added. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1590) Replace ParsedFile with Augeas

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-1590 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Replace ParsedFile with Augeas  
 
 
 
 
 
 
 
 
 
 
Another possibility is to leverage filemapper: https://github.com/voxpupuli/puppet-filemapper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-225) Support SCP for file transfer

2017-11-28 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-225 
 
 
 
  Support SCP for file transfer  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Labels:
 
 docs_reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7556) Type/Provider Improvements - Cron

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7556 
 
 
 
  Type/Provider Improvements - Cron   
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Team/s:
 
 Platform  Core  OS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7562) Type/Provider Improvements - Mount

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7562 
 
 
 
  Type/Provider Improvements - Mount  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Team/s:
 
 Platform  Core  OS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7564) augeas fixes

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7564 
 
 
 
  augeas fixes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Team/s:
 
 Platform  Core  OS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7546) PMT Improvements

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7546 
 
 
 
  PMT Improvements  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Team/s:
 
 Platform Core Puppet Developer Experience 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-226) Passing sudo-password with no value hangs when password is required

2017-11-28 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette commented on  BOLT-226 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Passing sudo-password with no value hangs when password is required  
 
 
 
 
 
 
 
 
 
 
Added a bug fix. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-226) Passing sudo-password with no value hangs when password is required

2017-11-28 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-226 
 
 
 
  Passing sudo-password with no value hangs when password is required  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Labels:
 
 resolved-issue-added 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-227) Bolt hangs if sudo password is invalid

2017-11-28 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette commented on  BOLT-227 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bolt hangs if sudo password is invalid  
 
 
 
 
 
 
 
 
 
 
Added a bug fix. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-227) Bolt hangs if sudo password is invalid

2017-11-28 Thread Michelle Fredette (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-227 
 
 
 
  Bolt hangs if sudo password is invalid  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Labels:
 
 resolved-issue-added 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8213) Error message for certificate name mismatch is clear as mud

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8213 
 
 
 
  Error message for certificate name mismatch is clear as mud  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Team:
 
 Platform Core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8211) Allow managehome to modify home directory for existing users

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8211 
 
 
 
  Allow managehome to modify home directory for existing users  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Issue Type:
 
 Bug New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8211) Allow managehome to modify home directory for existing users

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8211 
 
 
 
  Allow managehome to modify home directory for existing users  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Summary:
 
 User Resource Managehome not Working Properly Allow managehome to modify home directory for existing users 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8211) User Resource Managehome not Working Properly

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-8211 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: User Resource Managehome not Working Properly  
 
 
 
 
 
 
 
 
 
 
Unfortunately the documentation doesn't state this, but the managehome parameter only works if puppet creates the user account. Puppet does not currently modify existing users home directory. Since puppet has behaved this way for so long, I would consider this to be a new feature request (along with updating the docs to reflect current limitations). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7630) "Successful" puppet agent reports hide provider errors

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-7630 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Successful" puppet agent reports hide provider errors  
 
 
 
 
 
 
 
 
 
 
The whack-a-mole game is because the agent marks the report as failed if and only if any of the applied resources failed. The problem is there are many failure modes before we even start applying resources, e.g. instances, prefetch, loading cached catalog, cycles in the graph, loading providers with gem dependencies, etc. 
I don't know that determining report success/failure based on log message error levels will work in all cases, as some failures may not cause an error message to be emitted. 
I think a simpler solution may be to assume the report has failed in the beginning and only mark the report as successful if we apply the catalog successfully. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6739) Error running puppet with non-existent and non-default environment

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6739 
 
 
 
  Error running puppet with non-existent and non-default environment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Fix Version/s:
 
 PUP 5.y 
 
 
 

Fix Version/s:
 
 PUP 4.10.10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6739) Error running puppet with non-existent and non-default environment

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-6739 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error running puppet with non-existent and non-default environment  
 
 
 
 
 
 
 
 
 
 
Merged to 4.10.x in https://github.com/puppetlabs/puppet/commit/767c454bb6b8efa11bc3c1eb8252740050173749 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8213) Error message for certificate name mismatch is clear as mud

2017-11-28 Thread Charlie Sharpsteen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Charlie Sharpsteen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8213 
 
 
 
  Error message for certificate name mismatch is clear as mud  
 
 
 
 
 
 
 
 
 

Change By:
 
 Charlie Sharpsteen 
 
 
 

Affects Version/s:
 
 PUP 5.3.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8213) Error message for certificate name mismatch is clear as mud

2017-11-28 Thread Reid Vandewiele (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Reid Vandewiele commented on  PUP-8213 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error message for certificate name mismatch is clear as mud  
 
 
 
 
 
 
 
 
 
 
Here's a stack trace from when this error is thrown: 
 
 
 
 
 
 
Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=error: certificate verify failed: [ok for /CN=master-1.tld] 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/protocol.rb:44:in `connect_nonblock' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/protocol.rb:44:in `ssl_socket_connect' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/http.rb:948:in `connect' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/http.rb:887:in `do_start' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/http.rb:882:in `start' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/pool.rb:83:in `borrow' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/pool.rb:25:in `with_connection' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:305:in `with_connection' 

Jira (PUP-7630) "Successful" puppet agent reports hide provider errors

2017-11-28 Thread Charlie Sharpsteen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Charlie Sharpsteen commented on  PUP-7630 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Successful" puppet agent reports hide provider errors  
 
 
 
 
 
 
 
 
 
 
I think we keep playing whack-a-mole with this issue because our fixes are too specific. In the past it was about using a cached catalog. This ticket is about "provider errors". 
To put this one to bed, I think we have to go for a general solution: if the logs from the puppet run contain any message at error level, turn the node red in the console or otherwise flag it so that folks know it needs attention. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8213) Error message for certificate name mismatch is clear as mud

2017-11-28 Thread Reid Vandewiele (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Reid Vandewiele commented on  PUP-8213 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error message for certificate name mismatch is clear as mud  
 
 
 
 
 
 
 
 
 
 
Here's a stack trace from when this error is thrown. 
 
 
 
 
 
 
Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=error: certificate [204/1995] 
 
 
 
 
led: [ok for /CN=master-of-puppets-aws-1.sj.b2c.nike.com] 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/protocol.rb:44:in `connect_nonblock' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/protocol.rb:44:in `ssl_socket_connect' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/http.rb:948:in `connect' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/http.rb:887:in `do_start' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/http.rb:882:in `start' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/pool.rb:83:in `borrow' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/pool.rb:25:in `with_connection' 
 
 

Jira (PUP-8213) Error message for certificate name mismatch is clear as mud

2017-11-28 Thread Reid Vandewiele (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Reid Vandewiele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8213 
 
 
 
  Error message for certificate name mismatch is clear as mud  
 
 
 
 
 
 
 
 
 

Change By:
 
 Reid Vandewiele 
 
 
 

Comment:
 
 Here's a stack trace from when this error is thrown.{code}Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=error: certificate [204/1995]led: [ok for /CN=master-of-puppets-aws-1.sj.b2c.nike.com]/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/protocol.rb:44:in `connect_nonblock'/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/protocol.rb:44:in `ssl_socket_connect'/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/http.rb:948:in `connect'/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/http.rb:887:in `do_start'/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/http.rb:882:in `start'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/pool.rb:83:in `borrow'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/pool.rb:25:in `with_connection'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:305:in `with_connection'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:176:in `block in do_request'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:173:in `upto'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:173:in `do_request'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:79:in `get'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:153:in `http_request'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:132:in `http_get'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:208:in `block in search'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:256:in `block in do_request'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/request.rb:220:in `do_request'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:256:in `do_request'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:207:in `search'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/file_metadata/selector.rb:19:in `search'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:270:in `search'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file.rb:701:in `perform_recursion'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file.rb:670:in `block in recurse_remote_metadata'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file.rb:664:in `collect'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file.rb:664:in `recurse_remote_metadata'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file.rb:646:in `recurse_remote'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file.rb:569:in `recurse'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file.rb:470:in `eval_generate'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/additional_resource_generator.rb:56:in `eval_generate'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:112:in `block in evaluate'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:119:in `traverse'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:169:in `evaluate'/opt/puppetlabs/puppet/lib/ruby/vend

Jira (PUP-8213) Error message for certificate name mismatch is clear as mud

2017-11-28 Thread Reid Vandewiele (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Reid Vandewiele updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8213 
 
 
 
  Error message for certificate name mismatch is clear as mud  
 
 
 
 
 
 
 
 
 

Change By:
 
 Reid Vandewiele 
 
 
 

CS Priority:
 
 Needs Priority 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8213) Error message for certificate name mismatch is clear as mud

2017-11-28 Thread Reid Vandewiele (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Reid Vandewiele created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8213 
 
 
 
  Error message for certificate name mismatch is clear as mud  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/28 4:41 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Reid Vandewiele 
 
 
 
 
 
 
 
 
 
 
A common error in enterprise environments is a mismatch between the server setting on the agent and the common name of the master's cert / its dns alt names. 
Today, if this situation occurs the error message the agent prints is as clear as mud. For example: 
 
 
 
 
 
 
# You can't tell, but for this run server=master.tld 
 
 
 
 
#  
 
 
 
 
[root@aws-1 ssl]# puppet agent -t 
 
 
 
 
Warning: Unable to fetch my node definition, but the agent run will continue: 
 

Jira (PDB-2528) Expose PQL Parser in HTTP Endpoint

2017-11-28 Thread Steve Axthelm (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Axthelm commented on  PDB-2528 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Expose PQL Parser in HTTP Endpoint  
 
 
 
 
 
 
 
 
 
 
For the historical record, the query parameter is ast_only not parse_pql_only 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8127) Refactor error location strings to not use words for better I18n support

2017-11-28 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8127 
 
 
 
  Refactor error location strings to not use words for better I18n support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 For better translations we should look at how we add the location information to an error in 'ExternalFileError'. Instead of using words like 'at', 'at line', and 'in' we should change to something like ' [ ( file:line:pos ] ) '. Then we have no words to translate while still providing the location information.I think replacing the output with the below. Based on which variables are set the names on the left, would cause the output on the right:{code}file line pos ->  [  ( file:line:pos ] ) file line ->  [  ( file:line ] ) line pos ->  [  ( line:pos ] ) line ->  [  ( line ] ) {code}An example with all location information set{code}Error: Something went wrong  [  ( /Users/eric.delaney/work/my_repos/puppet/foo.pp:1:9 ] ) Error: Something went wrong  [  ( /Users/eric.delaney/work/my_repos/puppet/foo.pp:1 ] ) Error: Something went wrong  [  ( 1:9 ] ) Error: Something went wrong  [  ( 1 ] ) {code}Places that need to be updated:./puppet/error.rb - ExternalFileError -> to_s./puppet/parser/resource.rb - def merge(resource)./puppet/pops/validation.rb - DiagnosticFormatterPuppetStyle./puppet/util/errors.rb - Puppet::Util::Errors -> def error_context./puppet/util/log.rb - Puppet::Util::Log -> to_s line 403Some of the code that needs to be updated:{code}  module ExternalFileError# This module implements logging with a filename and line number. Use this# for errors that need to report a location in a non-ruby file that we# parse.attr_accessor :line, :file, :pos# May be called with 3 arguments for message, file, line, and exception, or# 4 args including the position on the line.#def initialize(message, file=nil, line=nil, pos=nil, original=nil)  if pos.kind_of? Exceptionoriginal = pospos = nil  end  super(message, original)  @file = file unless (file.is_a?(String) && file.empty?)  @line = line  @pos = posenddef to_s  msg = super  @file = nil if (@file.is_a?(String) && @file.empty?)  if @file and @line and @pos"#{msg} at #{@file}:#{@line}:#{@pos}"  elsif @file and @line"#{msg} at #{@file}:#{@line}"  elsif @line and @pos  "#{msg} at line #{@line}:#{@pos}"  elsif @line"#{msg} at line #{@line}"  elsif @file"#{msg} in #{@file}"  elsemsg  endend  end{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 

Jira (PUP-7507) puppet lookup --facts can't modify $facts hash

2017-11-28 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney commented on  PUP-7507 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup --facts  can't modify $facts hash  
 
 
 
 
 
 
 
 
 
 
Gerhardus Geldenhuis Could I get you to create a separate ticket for the 'trusted' case and what you see as the problem. That way we won't lose the issue and we can work on it there. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-239) command 'bolt --help' does not list short option for '--format' & does not list possible values

2017-11-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-239 
 
 
 
  command 'bolt --help' does not list short option for '--format' & does not list possible values  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 When I {code}bolt --help{code}I expected to see{code} -f, --format FORMAT  Output format to use: human, json{code} I currently see  {code}[root@qtum1nc8dkd1ufl ~]# bolt --helpUsage: bolt   [options]Available subcommands:bolt command runRun a command remotelybolt script run 

Jira (BOLT-239) command 'bolt --help' does not list short option for '--format' & does not list possible values

2017-11-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-239 
 
 
 
  command 'bolt --help' does not list short option for '--format' & does not list possible values  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 When I  `  {code} bolt --help `  {code}   I expected to see  ` {code}  -f, --format FORMAT  Output format to use: human, json `  {code}   {code}[root@qtum1nc8dkd1ufl ~]# bolt --helpUsage: bolt   [options]Available subcommands:bolt command runRun a command remotelybolt script run 

Jira (BOLT-239) command 'bolt --help' does not list short option for '--format' & does not list possible values

2017-11-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-239 
 
 
 
  command 'bolt --help' does not list short option for '--format' & does not list possible values  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 BOLT 0.9.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/28 2:25 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
When I `bolt --help` 
I expected to see `-f, --format FORMAT Output format to use: human, json` 
 
 
 
 
 
 
[root@qtum1nc8dkd1ufl ~]# bolt --help 
 
 
 
 
Usage: bolt   [options] 
 
 
 
 
  
 
 
 
  

Jira (PUP-8201) MAINTAINERS file needs maintenance

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-8201 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: MAINTAINERS file needs maintenance  
 
 
 
 
 
 
 
 
 
 
Gladly 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8201) MAINTAINERS file needs maintenance

2017-11-28 Thread Michael Stahnke (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Stahnke assigned an issue to Eric Sorenson 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8201 
 
 
 
  MAINTAINERS file needs maintenance  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Stahnke 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8201) MAINTAINERS file needs maintenance

2017-11-28 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  PUP-8201 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: MAINTAINERS file needs maintenance  
 
 
 
 
 
 
 
 
 
 
+1 kill it with �� 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8201) MAINTAINERS file needs maintenance

2017-11-28 Thread Michael Stahnke (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Stahnke commented on  PUP-8201 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: MAINTAINERS file needs maintenance  
 
 
 
 
 
 
 
 
 
 
It's used to build the maintainer mailing lists, and that's about it. Since that model was shifted and we now do teams owning maintenance, the easiest course of action might be to disable this whole workflow, delete the maintainer files and call it a day.  
Eric Sorenson thoughts?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-237) Bolt times out when running command on a host with a user that does not have password based login enabled

2017-11-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-237 
 
 
 
  Bolt times out when running command on a host with a user that does not have password based login enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Affects Version/s:
 
 BOLT 0.9.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-238) Passing anything to '--format' other than 'json' or 'human' results in a stacktrace

2017-11-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-238 
 
 
 
  Passing anything to '--format' other than 'json' or 'human' results in a stacktrace  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 BOLT 0.9.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/28 1:51 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
When using the command flag '--format' any option other than 'human' or 'json' results in a stack trace.  
 
 
 
 
 
 
[root@pwwayjdjwp58z7f ~]# bolt command run 'echo \"\"\"hello from $(hostname)\"\"\"' --nodes pwwayjdjwp58z7f.delivery.puppetlabs.net,e9zte871kphkgjm.delivery.puppetlabs.net -u root -p Qu@lity! --insecure  --format foo 
 
 
 
 
/usr/local/share/gems/gems/bolt-9.9.5bbba8c/lib/bolt/cli.rb:162:in `block (2 levels) in create_option_parser': undefined method `ArgumentError' for # (NoMethodError) 
 
 
 
 

Jira (BOLT-225) Support SCP for file transfer

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-225 
 
 
 
  Support SCP for file transfer  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Release Notes Summary:
 
 Bolt now uses scp to copy files to ssh targets instead of sftp. This means targets no longer need sftp configured. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-225) Support SCP for file transfer

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-225 
 
 
 
  Support SCP for file transfer  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Fix Version/s:
 
 BOLT 0.9.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7507) puppet lookup --facts can't modify $facts hash

2017-11-28 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-7507 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup --facts  can't modify $facts hash  
 
 
 
 
 
 
 
 
 
 
The PR does not address trusted facts (it was created before Gerhardus Geldenhuis replied to my question). 
Henrik Lindberg, I didn't perceive it as we reach a conclusion. Some of the trusted facts are derived from other facts and it's not trivial to just allow them to be overridden. It also raises a couple of questions. What would it meant to provide both 
 
 
 
 
 
 
{ 'clientcert' => 'some.domain.name' }
 
 
 
 
 
 
 
and 
 
 
 
 
 
 
{'trusted.domain' => 'other.name'}
 
 
 
 
 
 
 
? Also, should be allowed to override 'trusted.authenticated'? 
A middle ground could be to allow 'trusted.extensions' since they don't seem to be derived from anything. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 

Jira (BOLT-237) Bolt times out when running command on a host with a user that does not have password based login enabled

2017-11-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-237 
 
 
 
  Bolt times out when running command on a host with a user that does not have password based login enabled  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/28 1:32 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
[root@pwwayjdjwp58z7f ~]# bolt command run 'echo \"\"\"hello from $(hostname)\"\"\"' --nodes qlosttlbclkdzlq.delivery.puppetlabs.net -u root -p Qu@lity! --insecure  --format human 
 
 
 
 
Started on qlosttlbclkdzlq.delivery.puppetlabs.net... 
 
 
 
 
2017-11-28T21:29:45.212353  ERROR net.ssh.authentication.agent[fd8d38]: could not connect to ssh-agent: Agent not configured 
 
 
 
 
Failed on qlosttlbclkdzlq.delivery.puppetlabs.net: 
 
   

Jira (BOLT-72) Don't invoke new powershell instances

2017-11-28 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-72 
 
 
 
  Don't invoke new powershell instances  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Release Notes Summary:
 
 This improves performance of the  winrm  WinRM  transport by  reusing powershell instances  running PowerShell-based Bolt scripts and tasks in the connected WinRM session, rather than creating new PowerShell processes .  This also fixes an issue with properly reflecting failure status on PowerShell versions older than PowerShell 5.  Users should not rely on variables set between commands persisting , even those set in the $global scope .  Users should not rely on [Console]::WriteLine to produce output from PowerShell code. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-236) Allow private key path to be passed as a commandline option

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-236 
 
 
 
  Allow private key path to be passed as a commandline option  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Release Notes Summary:
 
 Bolt now supports a --private_key flag that specifies the private key file to use with the ssh transport. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 

Issue Type:
 
 Bug New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-227) Bolt hangs if sudo password is invalid

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-227 
 
 
 
  Bolt hangs if sudo password is invalid  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Release Notes Summary:
 
 Prevents bolt from hanging when attempting to sudo with the wrong password 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-227) Bolt hangs if sudo password is invalid

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-227 
 
 
 
  Bolt hangs if sudo password is invalid  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Fix Version/s:
 
 BOLT 0.9.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-44) Display human-readable results from running a task

2017-11-28 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  BOLT-44 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Display human-readable results from running a task  
 
 
 
 
 
 
 
 
 
 
Merged additional PR to master at https://github.com/puppetlabs/bolt/commit/68d7cfb82d247fdedb6522d36b2fea6fae5bc757 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-236) Allow private key path to be passed as a commandline option

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-236 
 
 
 
  Allow private key path to be passed as a commandline option  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Fix Version/s:
 
 0.9.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1542) Puppet::Util::Log requires a message

2017-11-28 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1542 
 
 
 
  Puppet::Util::Log requires a message  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8013) Translations should be stored in different text domains based on environment

2017-11-28 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8013 
 
 
 
  Translations should be stored in different text domains based on environment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Release Notes:
 
 New Feature Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7769) Provide a setting to disable translations

2017-11-28 Thread Melissa Amos (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Amos assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7769 
 
 
 
  Provide a setting to disable translations  
 
 
 
 
 
 
 
 
 

Change By:
 
 Melissa Amos 
 
 
 

Assignee:
 
 Melissa Amos 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8013) Translations should be stored in different text domains based on environment

2017-11-28 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8013 
 
 
 
  Translations should be stored in different text domains based on environment  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Release Notes Summary:
 
 Puppet will now correctly load module translations per environment. For example, if a user has two different versions of a module installed in two different environments, only the translations for the version in the requested environment will be loaded. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7507) puppet lookup --facts can't modify $facts hash

2017-11-28 Thread Gerhardus Geldenhuis (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gerhardus Geldenhuis commented on  PUP-7507 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup --facts  can't modify $facts hash  
 
 
 
 
 
 
 
 
 
 
Eric Delaney does this also resolve the issue for trusted facts? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8013) Translations should be stored in different text domains based on environment

2017-11-28 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone commented on  PUP-8013 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Translations should be stored in different text domains based on environment  
 
 
 
 
 
 
 
 
 
 
This has passed CI. Maggie Dreyer do we need any docs for this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7507) puppet lookup --facts can't modify $facts hash

2017-11-28 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney commented on  PUP-7507 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet lookup --facts  can't modify $facts hash  
 
 
 
 
 
 
 
 
 
 
Tested on SHA=5db2a7ea45c377429a62761b401ca066b55f15b6 SUITE_VERSION=1.10.8.116.g5db2a7e 
Using the reproduce above: 
 
 
 
 
 
 
[root@xltdnqmuemyejo7 ~]# puppet lookup ntp::servers --environment production --facts ./facts.yaml 
 
 
 
 
--- 1.2.3.4 
 
 
 
 
... 
 
 
 
 
[root@xltdnqmuemyejo7 ~]#
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "

Jira (BOLT-225) Support SCP for file transfer

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer assigned an issue to Alex Dreyer 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-225 
 
 
 
  Support SCP for file transfer  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Assignee:
 
 Alex Dreyer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7677) Create a feature flag setting for puppet 6 features during puppet 5 lifetime

2017-11-28 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney commented on  PUP-7677 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create a feature flag setting for puppet 6 features during puppet 5 lifetime  
 
 
 
 
 
 
 
 
 
 
Tested on SHA=a2e2fd14be88ac58a77db29685010783ca74d631 SUITE_VERSION=5.3.3.234.ga2e2fd1 
 
 
 
 
 
 
[root@x0kh2izaiejw5qz puppetlabs]# puppet config print future_features 
 
 
 
 
false 
 
 
 
 
[root@x0kh2izaiejw5qz puppetlabs]# puppet config set future_features true 
 
 
 
 
[root@x0kh2izaiejw5qz puppetlabs]# puppet config print future_features 
 
 
 
 
true 
 
 
 
 
[root@x0kh2izaiejw5qz puppetlabs]# cat /etc/puppetlabs/puppet/puppet.conf 
 
 
 
 
future_features = true 
 
 
 
 
# This file can be used to override the default puppet settings. 
 
 
 
 
# See the following links for more details on what settings are available: 
 
 
 
 
# - https://docs.puppetlabs.com/puppet/latest/reference/config_important_sett

Jira (PUP-7677) Create a feature flag setting for puppet 6 features during puppet 5 lifetime

2017-11-28 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7677 
 
 
 
  Create a feature flag setting for puppet 6 features during puppet 5 lifetime  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Fix Version/s:
 
 PUP 5.y 
 
 
 

Fix Version/s:
 
 PUP 5.4.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8107) Ability to specify source IP for the agent

2017-11-28 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-8107 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ability to specify source IP for the agent  
 
 
 
 
 
 
 
 
 
 
Merged to 4.10.x in https://github.com/puppetlabs/puppet/commit/ad78bd37cedbb95f7e17808316a13dece0fd3b4f 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-155) Show list of available tasks with bolt task show

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-155 
 
 
 
  Show list of available tasks with bolt task show  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Sprint:
 
 Bolt  Kanban  PuppetHack 2017 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-66) Run tasks through PAL so that arguments are validated

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-66 
 
 
 
  Run tasks through PAL so that arguments are validated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Sprint:
 
 Bolt  Kanban  PuppetHack 2017 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-225) Support SCP for file transfer

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-225 
 
 
 
  Support SCP for file transfer  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Sprint:
 
 Bolt  PuppetHack 2017  Kanban 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-225) Support SCP for file transfer

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-225 
 
 
 
  Support SCP for file transfer  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Issue Type:
 
 Bug Improvement 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-225) Support SCP for file transfer

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-225 
 
 
 
  Support SCP for file transfer  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 
 
 
 
 
 
 
 some sshd configurations allow ssh and scp commands but immediately close sftp connections without a useful message. Bolt should  probably  use scp  or fall back to scp if it can't open and  instead of  sftp  connection  for file transfers . Does this need to be a fla 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7779) Re-implement `puppet facts upload` and associated server endpoint

2017-11-28 Thread Verne Lindner (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Verne Lindner commented on  PUP-7779 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Re-implement `puppet facts upload` and associated server endpoint  
 
 
 
 
 
 
 
 
 
 
Ryan Coleman Please see CS priority remarks re: Tasks use. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-228) Improve Bolt testing helper Gem

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-228 
 
 
 
  Improve Bolt testing helper Gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Sprint:
 
 Bolt PuppetHack 2017 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-225) Support SCP for file transfer

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-225 
 
 
 
  Support SCP for file transfer  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Sprint:
 
 Bolt PuppetHack 2017 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-236) Allow private key path to be passed as a commandline option

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-236 
 
 
 
  Allow private key path to be passed as a commandline option  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/28 8:59 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Alex Dreyer 
 
 
 
 
 
 
 
 
 
 
The problem: When connecting to a remote VM without the default ssh private key (for example google_compute_engine), I was not able to choose which private key I want to use through CLI. 
2 Options: 
You can : $eval `ssh-add` && ssh-add ~/.ssh/ Run $bolt -i ~/.ssh/google_compute_engine ... or $bolt --private-key ~/.ssh/google_compute_engine I added tests for the CLI and to try connecting with specific private key using the Vagrantfile provided. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
 

Jira (BOLT-236) Allow private key path to be passed as a commandline option

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer assigned an issue to Alex Dreyer 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-236 
 
 
 
  Allow private key path to be passed as a commandline option  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Assignee:
 
 Alex Dreyer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-226) Passing sudo-password with no value hangs when password is required

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-226 
 
 
 
  Passing sudo-password with no value hangs when password is required  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Release Notes Summary:
 
 This prevents sudo from hanging when a password is expected but the user did not provide one 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-44) Display human-readable results from running a task

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-44 
 
 
 
  Display human-readable results from running a task  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Release Notes Summary:
 
 Improve the output for bolt command, script and task runs.  
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1542) Install Facter 3 as a gem

2017-11-28 Thread Owen Rodabaugh (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Rodabaugh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1542 
 
 
 
  Install Facter 3 as a gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Rodabaugh 
 
 
 

CS Impact:
 
 Without this most users are stuck doing automated testing with facter 2 which presents some risk if it differs from facter 3  and is end of life . Creating this facter 3 gem would be an enabler for testing workflows. There needs to be a plan for both automated testing, and also getting folks off the now EOL Facter2. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-72) Don't invoke new powershell instances

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-72 
 
 
 
  Don't invoke new powershell instances  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Release Notes Summary:
 
 This improves performance of the winrm transport by reusing powershell instances. Users should not rely on variables set between commands persisting. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-44) Display human-readable results from running a task

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-44 
 
 
 
  Display human-readable results from running a task  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Fix Version/s:
 
 BOLT 0.9.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1542) Install Facter 3 as a gem

2017-11-28 Thread Owen Rodabaugh (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Rodabaugh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1542 
 
 
 
  Install Facter 3 as a gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Rodabaugh 
 
 
 

CS Priority:
 
 Normal 
 
 
 

CS Impact:
 
 Without this most users are stuck doing automated testing with facter 2 which presents some risk if it differs from facter 3. Creating this facter 3 gem would be an enabler for testing workflows. 
 
 
 

CS Severity:
 
 3 - Serious 
 
 
 

CS Business Value:
 
 3 -  
 
 
 

CS Frequency:
 
 2 - 5-25% of Customers 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
 

Jira (BOLT-72) Don't invoke new powershell instances

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-72 
 
 
 
  Don't invoke new powershell instances  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Fix Version/s:
 
 BOLT 0.9.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7877) Future Work for Intermediate CA Improvements

2017-11-28 Thread Owen Rodabaugh (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Rodabaugh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7877 
 
 
 
  Future Work for Intermediate CA Improvements  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Rodabaugh 
 
 
 

CS Priority:
 
 Needs Priority Major 
 
 
 

CS Impact:
 
 Intermediate CAs are asked for by our largest users, as they are also very security conscious. While improvements were made to intermediate CAs in recent release they are still very difficult to setup and use and have some gaps as seen in the tickets within this epic.Improvements to the Intermediate CA would both improve the security aspects and also be an enabler for desired multi-datacenter/federated installation desired by many large customers, especially in the APJ region. 
 
 
 

CS Severity:
 
 3 - Serious 
 
 
 

CS Business Value:
 
 5 - $$ 
 
 
 

CS Frequency:
 
 2 - 5-25% of Customers 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 

Jira (BOLT-227) Bolt hangs if sudo password is invalid

2017-11-28 Thread Alex Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Dreyer assigned an issue to Alex Dreyer 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-227 
 
 
 
  Bolt hangs if sudo password is invalid  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Dreyer 
 
 
 

Assignee:
 
 Alex Dreyer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7779) Re-implement `puppet facts upload` and associated server endpoint

2017-11-28 Thread Owen Rodabaugh (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Rodabaugh updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7779 
 
 
 
  Re-implement `puppet facts upload` and associated server endpoint  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Rodabaugh 
 
 
 

CS Priority:
 
 Needs Priority Major 
 
 
 

CS Impact:
 
 Having fresh facts is only going to become higher priority as tasks become more popular and users get more experience with PQL for targeting them. This is also a big enabler of the direct puppet workflow. 
 
 
 

CS Severity:
 
 3 - Serious 
 
 
 

CS Business Value:
 
 5 - $$ 
 
 
 

CS Frequency:
 
 4 - 50-90% of Customers 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 

Jira (PUP-8204) loader.discover(:type) with --tasks on crashes because it tries to load rake tasks in puppet

2017-11-28 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8204 
 
 
 
  loader.discover(:type) with --tasks on crashes because it tries to load rake tasks in puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

QA Risk Assessment:
 
 Needs Assessment No Action 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8212) The Variant type without any types matches in strange ways

2017-11-28 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8212 
 
 
 
  The Variant type without any types matches in strange ways  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8212) The Variant type without any types matches in strange ways

2017-11-28 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-8212 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The Variant type without any types matches in strange ways  
 
 
 
 
 
 
 
 
 
 
This blocks PUP-8202 because it is searching for types that are assignable to the Task data type and it finds instances of the Variant data type in error. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8212) The Variant type without any types matches in strange ways

2017-11-28 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8212 
 
 
 
  The Variant type without any types matches in strange ways  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/28 7:23 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
The Variant type when used as just Variant (no list of types) has an implementation that uses all? to check if all types in a RHS variant can be assigned to the LHS type. This fails when the RHS Variant is empty. 
An empty Variant should only be assignable from a Variant as the only meaningful interpretation of a Variant without any types to perform an OR matching operation on is that it means "all types that are actually Variant". 
If an empty Variant was to be interpreted as Variant[Any}, then it is essentially the same as Any, and that is surprising. 
If it was to be an error to use Variant as an _expression_, we need to change the entire implementation how parameterized types are formed using the AST. (It has one _expression_ that evaluates to the base Variant type, followed by an "at" _expression_ [T1, T2,...] that constrains/widens/defines the type instance that will be created. 
When fixing this, there are numerous tests that include the Variant in the list of "all types", and this change will require a special section of tests for the Variant type. 
As the result when using a "naked" Variant is both conceptually wrong and confusing, this is going to be fixed on our oldest supported version in 4.x. 
 
 
 
 
 
 
 
 
 
 

Jira (PUP-8078) Make it possible to create parameterized Object data types

2017-11-28 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8078 
 
 
 
  Make it possible to create parameterized Object data types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Release Notes Summary:
 
 This is mostly an internal concern when implementing new types (needed this for Bolt related data types like Error). 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


  1   2   >