Jira (PUP-8406) Puppet Error datatype uses 'message' not 'msg' as hash key

2018-01-31 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8406 
 
 
 
  Puppet Error datatype uses 'message' not 'msg' as hash key  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-291) Task show displays a confusing type for empty parameters

2018-01-31 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-291 
 
 
 
  Task show displays a confusing type for empty parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Release Notes Summary:
 
 Previously if a user did not specify a 'type' in a tasks metadata for a given parameter, bolt would tell the user that the type was 'Data'.  Now when a user uses the command 'bolt task show ' bolt will describe a parameter without a type and list its type as 'Any'.    
 
 
 

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-291) Task show displays a confusing type for empty parameters

2018-01-30 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-291 
 
 
 
  Task show displays a confusing type for empty parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-230) Build helper for Bolt installation

2018-01-30 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-230 
 
 
 
  Build helper for Bolt installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Sprint:
 
 Bolt 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-230) Build helper for Bolt installation

2018-01-30 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-230 
 
 
 
  Build helper for Bolt installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-230) Build helper for Bolt installation

2018-01-30 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-230 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build helper for Bolt installation  
 
 
 
 
 
 
 
 
 
 
As I am leaving I am unsure who would be responsible for advancing this. I'm going to leave a list of questions here for posterity. 
 

Currently this tool pins to bolt 0.7.0
 

* In the future I think we would want to install the latest
 

* This would require maintenance to this tool as breaking changes occur
 

This tool doesn't yet manage the ruby version on the system that accepts Bolt
 

This tool is not able to install/run bolt on the test coordinator
 

In the modules tests they run a bolt command against 'localhost'
 

* This will need to change in the future
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

Jira (BOLT-304) Show parameter names and types with bolt plan show

2018-01-30 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-304 
 
 
 
  Show parameter names and types with bolt plan show   
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Fix Version/s:
 
 BOLT 0.16.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-320) User has no way of knowing what the default value for a parameter in a plan is

2018-01-29 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-320 
 
 
 
  User has no way of knowing what the default value for a parameter in a plan is   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 BOLT 0.15.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2018/01/29 2:52 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
Given the following plan 
 
 
 
 
 
 
plan test2( 
 
 
 
 
  String $nodes, Optional[String] $rubber, Array $baby, Enum['on', 'off'] $buggy, String $bumpers = 'bar') { 
 
 
 
 
}
 
 
 
 
 
  

Jira (BOLT-319) 'bolt plan show' list unusable usage when parameters are typed

2018-01-29 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-319 
 
 
 
  'bolt plan show' list unusable usage when parameters are typed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 BOLT 0.15.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2018/01/29 2:46 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
Given the following plan 
 
 
 
 
 
 
init.pp 
 
 
 
 
 
 
plan test2( 
 
 
 
 
  String $nodes, Optional[String] $rubber, Array $baby, Enum['on', 'off'] $buggy, String $bumpers = 'bar') { 
 
 
  

Jira (BOLT-304) Show parameter names and types with bolt plan show

2018-01-29 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-304 
 
 
 
  Show parameter names and types with bolt plan show   
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Michal Ruzicka Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-290) Decompose --insecure flag

2018-01-25 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-290 
 
 
 
  Decompose --insecure flag  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-277) SSL default makes winrm harder to use

2018-01-23 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-277 
 
 
 
  SSL default makes winrm harder to use  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-277) SSL default makes winrm harder to use

2018-01-23 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-277 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SSL default makes winrm harder to use  
 
 
 
 
 
 
 
 
 
 
Alex Dreyer I just tested with whats on the master branch (0df4ad4f8eff1decce14ff9e1be6e4b8fa3a7bec). I'm not seeing an mention of `-

insecure` when I attempt to run a plan over winrm without `
-insecure`  
 
 
 
 
 
 
[root@jglk6mp8lkkbjjn ~]# bolt plan run test::my_win_plan nodes=winrm://a096ly48bagmce7.delivery.puppetlabs.net,winrm://rjintdso3lglsox.delivery.puppetlabs.net --modulepath /tmp/C100554.g0DmW1/modules -u Administrator -p Qu@lity! --verbose 
 
 
 
 
Warning: Support for ruby version 2.0.0 is deprecated and will be removed in a future release. See https://docs.puppet.com/puppet/latest/system_requirements.html#ruby for a list of supported ruby versions. 
 
 
 
 
   (at /usr/local/share/gems/gems/bolt-9.9.0df4ad4/vendored/puppet/lib/puppet.rb:130:in `') 
 
 
 
 
2018-01-23T18:48:03.943247 INFO   Bolt::Executor: Starting task /tmp/C100554.g0DmW1/modules/test/tasks/a_win.ps1 on ["winrm://a096ly48bagmce7.delivery.puppetlabs.net", "winrm://rjintdso3lglsox.delivery.puppetlabs.net"] 
 
 
 
 
2018-01-23T18:48:13.984342 INFO   Bolt::Executor: Ran task '/tmp/C100554.g0DmW1/modules/test/tasks/a_win.ps1' on 2 nodes with 2 failures 
 
 
 
 
Evaluation Error: Error while evaluating a Function Call, Plan aborted: run_task 'test::a_win' failed on 2 nodes at /tmp/C100554.g0DmW1/modules/test/plans/my_win_plan.pp:3:17
 
 
 
 
 
 
 
 
 
 
 
 

Jira (BOLT-311) Error from run_task plan causes uncaught exception

2018-01-22 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-311 
 
 
 
  Error from run_task plan causes uncaught exception  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-277) SSL default makes winrm harder to use

2018-01-22 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-277 
 
 
 
  SSL default makes winrm harder to use  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-277) SSL default makes winrm harder to use

2018-01-22 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-277 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SSL default makes winrm harder to use  
 
 
 
 
 
 
 
 
 
 
I see new messaging when a user runs a task. 
 
 
 
 
 
 
Started on sjgst1q2206djv5.delivery.puppetlabs.net... 
 
 
 
 
Failed on sjgst1q2206djv5.delivery.puppetlabs.net: 
 
 
 
 
  Timeout after 10 seconds connecting to https://sjgst1q2206djv5.delivery.puppetlabs.net:5986/wsman 
 
 
 
 
  Use --insecure if this host isn't configured to use SSL for WinRM
 
 
 
 
 
 
 
However I don't see any messaging when a task is run through a plan 
 
 
 
 
 
 
2018-01-22T12:43:38.273348 INFO   Bolt::Executor: Starting task /tmp/C100554.5fjVHH/modules/test/tasks/a_win.ps1 on ["winrm://sjgst1q2206djv5.delivery.puppetlabs.net"] 
 
 
 
 
2018-01-22T12:43:48.278445 INFO   Bolt::Executor: Ran task '/tmp/C100554.5fjVHH/modules/test/tasks/a_win.ps1' on 1 node with 1 failure 
 
 
 
 
Evaluation Error: Error while evaluating a Function Call, Plan aborted: run_task 'test::a_win' failed on 1 nodes at /tmp/C100554.5fjVHH/modules/test/plans/my_win_plan.pp:3:17
 
 
 
 
 
 

Jira (BOLT-289) Standardize Target object

2018-01-19 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-289 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Standardize Target object  
 
 
 
 
 
 
 
 
 
 
I attempted to to run a plan that does not split the nodes into an Array but instead hands the comma seperated String to `run_task` {code, title=ssh_plan.pp} 
plan test::my_unix_plan($nodes) { notice("$ {run_task(test::a_unix, $nodes)} 
") notice("$ {run_task(test::b_unix, $nodes)} 
") } 
 
 
 
 
 
 
  
 
 
 
 
In this example bolt is running on centos7 and the target nodes are centos7 and ubuntu 16.04 
 
 
 
 
  
 
 
 
 
Here is the output from running this plan 
 
 
 
 
{code, title=output} 
 
 
 
 
i2p9enstpbdld5i.delivery.puppetlabs.net (centos7-64-1) 10:02:11$ bolt plan run test::my_unix_plan nodes=i2p9enstpbdld5i.delivery.puppetlabs.net,d5q9buobh8s2b15.delivery.puppetlabs.net -u root --modulepath /tmp/C100553.f7l1k0/modules -p Qu@lity! --insecure 
 
 
 
 
  Warning: Support for ruby version 2.0.0 is deprecated and will be removed in a future release. See https://docs.puppet.com/puppet/latest/system_requirements.html#ruby for a list of supported ruby versions. 
 
 
 
 
 (at /usr/local/share/gems/gems/bolt-9.9.66ed6d2/vendored/puppet/lib/puppet.rb:130:in `') 
 
 
 

Jira (BOLT-289) Standardize Target object

2018-01-18 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-289 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Standardize Target object  
 
 
 
 
 
 
 
 
 
 
Alex Dreyer You mentioned that this could affect how a user could write a plan? Can you detail how a plan would be impacted by this change.  
Is the signature still the same for run_* functions? 
 
 
 
 
 
 
run_task(test::a_unix, $nodes_array)
 
 
 
 
 
 
 
and/or is there new functionality that a user can make use of in the Bolt::Result ?  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-290) Decompose --insecure flag

2018-01-12 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-290 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Decompose --insecure flag  
 
 
 
 
 
 
 
 
 
 
You are correct, reverse that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-290) Decompose --insecure flag

2018-01-12 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-290 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Decompose --insecure flag  
 
 
 
 
 
 
 
 
 
 
Alex Dreyer Should `--[no-]host-key-check` just be ignored for SSH? Same question for --[no-]ssl with WINRM only WINRM nodes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-290) Decompose --insecure flag

2018-01-12 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-290 
 
 
 
  Decompose --insecure flag  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-295) Run any script with extension handler on Windows

2018-01-11 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-295 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Run any script with extension handler on Windows  
 
 
 
 
 
 
 
 
 
 
Bolt seems to exit 0 if an extension is not configured on a node. Is this the correct behavior? 
 
 
 
 
 
 
[6] pry(#)> result = bolt_command_on(bolt, bolt_command, flags) 
 
 
 
 
  
 
 
 
 
tlr76ts71drauxh.delivery.puppetlabs.net (centos7-64-1) 08:33:46$ bolt script run C100549.exe --nodes winrm://nkydbnrbt5sxqb6.delivery.puppetlabs.net -u Administrator -p Qu@lity! --insecure 
 
 
 
 
  Started on nkydbnrbt5sxqb6.delivery.puppetlabs.net... 
 
 
 
 
  Failed on nkydbnrbt5sxqb6.delivery.puppetlabs.net: 
 
 
 
 
File extension .exe is not enabled, to run it please add to 'winrm: extensions' 
 
 
 
 
  Ran on 1 node in 0.33 seconds 
 
 
 
 
  
 
 
 
 
tlr76ts71drauxh.delivery.puppetlabs.net (centos7-64-1) executed in 0.79 seconds 
 
 
 
 
  

Jira (BOLT-295) Run any script with extension handler on Windows

2018-01-11 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-295 
 
 
 
  Run any script with extension handler on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-285) Bolt should handle parser errors better

2018-01-11 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-285 
 
 
 
  Bolt should handle parser errors better  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-266) Log run_* actions when called from a plan

2018-01-10 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-266 
 
 
 
  Log run_* actions when called from a plan  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-281) Update writing tasks doc

2018-01-08 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-281 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Update writing tasks doc  
 
 
 
 
 
 
 
 
 
 
Michelle Fredette I have attached the file that we merged into the hands on lab. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-281) Update writing tasks doc

2018-01-08 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-281 
 
 
 
  Update writing tasks doc  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Attachment:
 
 file.py 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8298) Add new issue type INVALID_TASK_NAME

2018-01-04 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Alex Dreyer 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8298 
 
 
 
  Add new issue type INVALID_TASK_NAME  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Lucy Wyman 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-283) The run_task function should verify that the parameters are Data

2018-01-04 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-283 
 
 
 
  The run_task function should verify that the parameters are Data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Fix Version/s:
 
 BOLT 0.13.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-284) task show displays more verbose parameter type than described

2018-01-04 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-284 
 
 
 
  task show displays more verbose parameter type than described  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-213) Bolt plan help includes --nodes

2018-01-02 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-213 
 
 
 
  Bolt plan help includes --nodes  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-281) --noop example task is broken

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-281 
 
 
 
  --noop example task is broken   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/28 1:33 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
In creating a new lesson for the hands-on-lab I used this example task as the basis for the lesson. In testing it I found that it was not working in manny cases. This PR improves the task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (BOLT-281) --noop example task is broken

2017-12-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-281 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: --noop example task is broken   
 
 
 
 
 
 
 
 
 
 
Once my PR is merged into the hands-on-lab I will merge the same task into the repo for the docs.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-279) '_error' key is ignored by bolt if task does not exit 1

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-279 
 
 
 
  '_error' key is ignored by bolt if task does not exit 1  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Sub-team:
 
 Bolt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-280) Bolt returns stack trace when modulepath is not accessible by current user

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-280 
 
 
 
  Bolt returns stack trace when modulepath is not accessible by current user  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/28 11:10 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
[foo@hcxvukp13xwbpap tasks]$ bolt task run exercize8::file --modulepath /tmp/moduels/ --nodes localhost --insecure -pQu@lity! filename=/tmp/hello_world content=foobar 
 
 
 
 
Warning: Support for ruby version 2.0.0 is deprecated and will be removed in a future release. See https://docs.puppet.com/puppet/latest/system_requirements.html#ruby for a list of supported ruby versions. 
 
 
 
 
   (at /usr/local/share/gems/gems/bolt-9.9.2f95814/vendored/puppet/lib/puppet.rb:130:in `') 
 
 
 
 

Jira (BOLT-279) '_error' key is ignored by bolt if task does not exit 1

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-279 
 
 
 
  '_error' key is ignored by bolt if task does not exit 1  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 Given the following task{code:name=test_task.py}result = {"_error": { "kind": "file_error", "msg": msg, "details": {}, }}print(json.dumps(result))exit(0){code}bolt ignores the error key{code}bolt task run test::test_task Finished on localhost:  {  }Ran on 1 node in 0.64 seconds{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-279) '_error' key is ignored by bolt if task does not exit 1

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-279 
 
 
 
  '_error' key is ignored by bolt if task does not exit 1  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/28 9:14 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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, 

Jira (BOLT-271) Update Hands on Lab to use metadata features

2017-12-21 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-271 
 
 
 
  Update Hands on Lab to use metadata features  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-8271) init plans in bolt do not load correctly from 'bolt plan show'

2017-12-20 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8271 
 
 
 
  init plans in bolt do not load correctly from 'bolt plan show'  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 

Created:
 

 2017/12/20 11:36 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
*Puppet Version: vendored  branch = feature_puppet-tasks 
Describe your issue in as much detail as possible… Describe steps to reproduce… 
Desired Behavior: 
*Actual Behavior: Given the following plan 
 
 
 
 
 
 
modules/foo/plans/init.pp 
 
 
 
 
 
 
plan foo() { 
 
 
 
 
  notice 'I am the init plan for the foo module' 
 
 
 
 

Jira (BOLT-32) Add ability to enumerate available plans

2017-12-20 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Alex Dreyer 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-32 
 
 
 
  Add ability to enumerate available plans  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 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-275) Bolt plan example contains error

2017-12-20 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-275 
 
 
 
  Bolt plan example contains error  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/20 8:57 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
In the documentation https://puppet.com/docs/bolt/0.x/writing_plans.html#defining-plan-parameters 
The example will not compile, the variant declarations need closing brackets. 
It should be 
 
 
 
 
 
 
plan mymodule::my_plan( 
 
 
 
 
  String[1]$load_balancer,  
 
 
 
 
  Variant[String[1], Array[String[1]]]  $frontends, 
 
 
 
 
  Variant[String[1], Array[String[1]]]  $backends, 
 

Jira (BOLT-32) Add ability to enumerate available plans

2017-12-20 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-32 
 
 
 
  Add ability to enumerate available plans  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32) Add ability to enumerate available plans

2017-12-20 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-32 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add ability to enumerate available plans  
 
 
 
 
 
 
 
 
 
 
It looks like the docs reference the ability to make an init plan. If I have a plan like this 
 
 
 
 
 
 
plan foo() { 
 
 
 
 
  notice 'I am the init plan for the foo module' 
 
 
 
 
}
 
 
 
 
 
 
 
And I use 'bolt plan show', I get the following. 
 
 
 
 
 
 
[root@p0dv972ia1yz1v1 ~]# bolt plan show --modulepath ~/modules 
 
 
 
 
Warning: Support for ruby version 2.0.0 is deprecated and will be removed in a future release. See https://docs.puppet.com/puppet/latest/system_requirements.html#ruby for a list of supported ruby versions. 
 
 
 
 
   (at /usr/local/share/gems/gems/bolt-9.9.afe6bdc/vendored/puppet/lib/puppet.rb:130:in `') 
 
 
 
 
Error: The code loaded from /root/modules/foo/plans/init.pp produced plan with the wrong name, expected foo::init, actual foo on node p0dv972ia1yz1v1.delivery.puppetlabs.net 
 
 
 
 
Failure while reading plans
 
 
  

Jira (BOLT-270) Bolt should use cacert (not ca-cert) for consistency with other Puppet tools

2017-12-20 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-270 
 
 
 
  Bolt should use cacert (not ca-cert) for consistency with other Puppet tools  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-252) Run Bolt acceptance tests on merge

2017-12-18 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-252 
 
 
 
  Run Bolt acceptance tests on merge  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Nick Lewis Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-261) Quoted class task name should not work as a reference to a task in a plan

2017-12-18 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-261 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Quoted class task name should not work as a reference to a task in a plan  
 
 
 
 
 
 
 
 
 
 
We currently enforce lower_snake_case for task names. https://puppet.com/docs/bolt/0.x/writing_tasks.html#naming-tasks At least in PE.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-125) Support WinRM over SSL

2017-12-14 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-125 
 
 
 
  Support WinRM over SSL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-261) Quoted class task name should not work as a reference to a task in a plan

2017-12-13 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-261 
 
 
 
  Quoted class task name should not work as a reference to a task in a plan  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 BOLT 0.11.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/13 12:11 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
When I create the following plan: 
 
 
 
 
 
 
plan test::my_unix_plan($nodes) { 
 
 
 
 
  $nodes_array = $nodes.split(',') 
 
 
 
 
  run_task('Test::A_unix', $nodes_array) 
 
 
 
 

Jira (BOLT-251) Incorrectly escaped windows path passed to 'tmpdir' results in stack trace

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-251 
 
 
 
  Incorrectly escaped windows path passed to 'tmpdir' results in stack trace  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 BOLT 0.10.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/12/11 10:28 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
When I attempt to pass tmpdir a Windows path with a single backslash  
 
 
 
 
 
 
--- 
 
 
 
 
winrm: 
 
 
 
 
  tmpdir: "C:\foo" 
 
 
 
 

 

Jira (BOLT-229) Enable helper to execute bolt on Test coordinator & SUT

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-229 
 
 
 
  Enable helper to execute bolt on Test coordinator & SUT  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

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-232) Add acceptance tests for Bolt task helper

2017-11-30 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-232 
 
 
 
  Add acceptance tests for Bolt task helper  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-231) Build testing/release pipeline for Bolt task helper

2017-11-30 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-231 
 
 
 
  Build testing/release pipeline for Bolt task helper  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-229) Enable helper to execute bolt on Test coordinator & SUT

2017-11-30 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-229 
 
 
 
  Enable helper to execute bolt on Test coordinator & SUT  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-230) Build helper for Bolt installation

2017-11-30 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-230 
 
 
 
  Build helper for Bolt installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-231) Build testing/release pipeline for Bolt task helper

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-231 
 
 
 
  Build testing/release pipeline for Bolt task helper  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Parent:
 
 BOLT-228 
 
 
 

Issue Type:
 
 Sub-task Task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-230) Build helper for Bolt installation

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-230 
 
 
 
  Build helper for Bolt installation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Parent:
 
 BOLT-228 
 
 
 

Issue Type:
 
 Sub-task Task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-229) Enable helper to execute bolt on Test coordinator & SUT

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-229 
 
 
 
  Enable helper to execute bolt on Test coordinator & SUT  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Parent:
 
 BOLT-228 
 
 
 

Issue Type:
 
 Sub-task Task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-232) Add acceptance tests for Bolt task helper

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-232 
 
 
 
  Add acceptance tests for Bolt task helper  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Parent:
 
 BOLT-228 
 
 
 

Issue Type:
 
 Sub-task Task 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-242) Using '-v' flag results in stack trace

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-242 
 
 
 
  Using '-v' flag results in stack trace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 I attempted to try and use the  '  ` -v ' `  flag thinking it was short for   '   ` --verbose ' ` .  I get the following{code}[root@x0x05i5yhvg7vs7 ~]# bolt -v/usr/local/share/gems/gems/bolt-9.9.8ee85bd/lib/bolt/cli.rb:227:in `block in parse': ambiguous option: -v (OptionParser::AmbiguousOption) from /usr/local/share/gems/gems/bolt-9.9.8ee85bd/lib/bolt/cli.rb:367:in `handle_parser_errors' from /usr/local/share/gems/gems/bolt-9.9.8ee85bd/lib/bolt/cli.rb:226:in `parse' from /usr/local/share/gems/gems/bolt-9.9.8ee85bd/exe/bolt:8:in `' from /usr/local/bin/bolt:23:in `load' from /usr/local/bin/bolt:23:in `'{code}Since '-v' is not a valid flag I expected to see the following{code}[root@x0x05i5yhvg7vs7 ~]# bolt --fooUnknown argument '--foo'{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-242) Using '-v' flag results in stack trace

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-242 
 
 
 
  Using '-v' flag results in stack trace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 I attempted to try and use the `-v` flag thinking it was short for  ` -- verbose`.  I get the following{code}[root@x0x05i5yhvg7vs7 ~]# bolt -v/usr/local/share/gems/gems/bolt-9.9.8ee85bd/lib/bolt/cli.rb:227:in `block in parse': ambiguous option: -v (OptionParser::AmbiguousOption) from /usr/local/share/gems/gems/bolt-9.9.8ee85bd/lib/bolt/cli.rb:367:in `handle_parser_errors' from /usr/local/share/gems/gems/bolt-9.9.8ee85bd/lib/bolt/cli.rb:226:in `parse' from /usr/local/share/gems/gems/bolt-9.9.8ee85bd/exe/bolt:8:in `' from /usr/local/bin/bolt:23:in `load' from /usr/local/bin/bolt:23:in `'{code}Since '-v' is not a valid flag I expected to see the following{code}[root@x0x05i5yhvg7vs7 ~]# bolt --fooUnknown argument '--foo'{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-242) Using '-v' flag results in stack trace

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-242 
 
 
 
  Using '-v' flag results in stack trace  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 BOLT 0.9.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/29 3:31 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
I attempted to try and use the '

v' flag thinking it was short for '
-verbose'.  I get the following 
 
 
 
 
 
 
[root@x0x05i5yhvg7vs7 ~]# bolt -v 
 
 
 
 
/usr/local/share/gems/gems/bolt-9.9.8ee85bd/lib/bolt/cli.rb:227:in `block in parse': ambiguous option: -v (OptionParser::AmbiguousOption) 
 
 
 
 
	from 

Jira (BOLT-242) Using '-v' flag results in stack trace

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-242 
 
 
 
  Using '-v' flag results in stack trace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 I attempted to try and use the '-v' flag thinking it was short for '--verbose'.  I get the following{code}[root@x0x05i5yhvg7vs7 ~]# bolt -v/usr/local/share/gems/gems/bolt-9.9.8ee85bd/lib/bolt/cli.rb:227:in `block in parse': ambiguous option: -v (OptionParser::AmbiguousOption) from /usr/local/share/gems/gems/bolt-9.9.8ee85bd/lib/bolt/cli.rb:367:in `handle_parser_errors' from /usr/local/share/gems/gems/bolt-9.9.8ee85bd/lib/bolt/cli.rb:226:in `parse' from /usr/local/share/gems/gems/bolt-9.9.8ee85bd/exe/bolt:8:in `' from /usr/local/bin/bolt:23:in `load' from /usr/local/bin/bolt:23:in `'{code}Since '-v' is not a valid flag I expected to see the following{code}[root@x0x05i5yhvg7vs7 ~]# bolt --fooUnknown argument '--foo'{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-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 (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-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-228) Improve Bolt testing helper Gem

2017-11-21 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-232) Add acceptance tests for Bolt task helper

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-232 
 
 
 
  Add acceptance tests for Bolt task helper  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/21 8:29 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

Jira (BOLT-231) Build testing/release pipeline for Bolt task helper

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-231 
 
 
 
  Build testing/release pipeline for Bolt task helper  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/21 8:28 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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, 

Jira (BOLT-230) Build helper for Bolt installation

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-230 
 
 
 
  Build helper for Bolt installation  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/21 8:27 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
Enable installation on: 
 

Beaker SUT
 

Beaker Coordinator
 
 
Install from: 
 

git repository
 

gem source
 

local directory
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
   

Jira (BOLT-229) Enable helper to execute bolt on Test coordinator & SUT

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-229 
 
 
 
  Enable helper to execute bolt on Test coordinator & SUT  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Sub-task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/21 8:24 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
The test helper should be able to execute a bolt command on the Test coordinator node and a System Under Test, through Beaker.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (BOLT-228) Improve Bolt testing helper Gem

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

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

Change By:
 
 Zach Reichert 
 
 
 

Sub-team:
 
 Bolt 
 
 
 

Team:
 
 Direct Change 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-21 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert created an issue 
 
 
 
 
 
 
 
 
 
 

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

Issue Type:
 
  Story 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/21 8:21 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

Jira (BOLT-220) Acceptance test for sudo support

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-220 
 
 
 
  Acceptance test for sudo support  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/16 2:59 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

Jira (BOLT-214) Set up publicly accessible acceptance testing for Bolt

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-214 
 
 
 
  Set up publicly accessible acceptance testing for Bolt  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Story 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/15 11:51 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
As a open source contributor to the Bolt project  I would like to run the acceptance test when I make a pull request So that I can be confident that my change did not break Bolt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (BOLT-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-209 
 
 
 
  Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 *Given *An empty known_hosts file  *When *{code}mvaypj4nxldckoj.delivery.puppetlabs.net (centos7-64-1) 14:32:31$ bolt command run 'echo """hello from $(hostname)"""' --nodes mvaypj4nxldckoj.delivery.puppetlabs.net,ucqxte3fgv2l7v7.delivery.puppetlabs.net,odcckquiw5m46l9.delivery.puppetlabs.net -u root -p Qu@lity!  mvaypj4nxldckoj.delivery.puppetlabs.net:  Host key verification failed for mvaypj4nxldckoj.delivery.puppetlabs.net: fingerprint 7a:78:5a:da:31:f5:b7:68:b8:4a:49:92:30:cb:48:ee is unknown for "mvaypj4nxldckoj.delivery.puppetlabs.net,10.32.122.70"  ucqxte3fgv2l7v7.delivery.puppetlabs.net:  Host key verification failed for ucqxte3fgv2l7v7.delivery.puppetlabs.net: fingerprint 9d:b1:85:d4:b2:4a:73:d2:aa:7a:8c:f7:bd:08:c2:d3 is unknown for "ucqxte3fgv2l7v7.delivery.puppetlabs.net,10.32.119.57"  odcckquiw5m46l9.delivery.puppetlabs.net:  Host key verification failed for odcckquiw5m46l9.delivery.puppetlabs.net: fingerprint 23:d3:c3:60:24:40:08:55:e6:db:16:cb:95:f9:5f:90 is unknown for "odcckquiw5m46l9.delivery.puppetlabs.net,10.32.124.170"  Ran on 3 nodes in 0.07 seconds{code}*Then*I expect to see a non-zero exit code{code}[1] pry(#)> result.exit_code=> 0{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 

Jira (BOLT-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-209 
 
 
 
  Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 *Given *An empty known_hosts file*When *{code}mvaypj4nxldckoj.delivery.puppetlabs.net (centos7-64-1) 14:32:31$ bolt command run 'echo """hello from $(hostname)"""' --nodes mvaypj4nxldckoj.delivery.puppetlabs.net,ucqxte3fgv2l7v7.delivery.puppetlabs.net,odcckquiw5m46l9.delivery.puppetlabs.net -u root -p Qu@lity!  mvaypj4nxldckoj.delivery.puppetlabs.net:  Host key verification failed for mvaypj4nxldckoj.delivery.puppetlabs.net: fingerprint 7a:78:5a:da:31:f5:b7:68:b8:4a:49:92:30:cb:48:ee is unknown for "mvaypj4nxldckoj.delivery.puppetlabs.net,10.32.122.70"  ucqxte3fgv2l7v7.delivery.puppetlabs.net:  Host key verification failed for ucqxte3fgv2l7v7.delivery.puppetlabs.net: fingerprint 9d:b1:85:d4:b2:4a:73:d2:aa:7a:8c:f7:bd:08:c2:d3 is unknown for "ucqxte3fgv2l7v7.delivery.puppetlabs.net,10.32.119.57"  odcckquiw5m46l9.delivery.puppetlabs.net:  Host key verification failed for odcckquiw5m46l9.delivery.puppetlabs.net: fingerprint 23:d3:c3:60:24:40:08:55:e6:db:16:cb:95:f9:5f:90 is unknown for "odcckquiw5m46l9.delivery.puppetlabs.net,10.32.124.170"  Ran on 3 nodes in 0.07 seconds{code}*Then*I expect to see a non-zero exit code{code}[1] pry(#)> result.exit_code=> 0{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 

Jira (BOLT-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-209 
 
 
 
  Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 * Given    * An empty known_hosts file * When    * {code}mvaypj4nxldckoj.delivery.puppetlabs.net (centos7-64-1) 14:32:31$ bolt command run 'echo """hello from $(hostname)"""' --nodes mvaypj4nxldckoj.delivery.puppetlabs.net,ucqxte3fgv2l7v7.delivery.puppetlabs.net,odcckquiw5m46l9.delivery.puppetlabs.net -u root -p Qu@lity!  mvaypj4nxldckoj.delivery.puppetlabs.net:  Host key verification failed for mvaypj4nxldckoj.delivery.puppetlabs.net: fingerprint 7a:78:5a:da:31:f5:b7:68:b8:4a:49:92:30:cb:48:ee is unknown for "mvaypj4nxldckoj.delivery.puppetlabs.net,10.32.122.70"  ucqxte3fgv2l7v7.delivery.puppetlabs.net:  Host key verification failed for ucqxte3fgv2l7v7.delivery.puppetlabs.net: fingerprint 9d:b1:85:d4:b2:4a:73:d2:aa:7a:8c:f7:bd:08:c2:d3 is unknown for "ucqxte3fgv2l7v7.delivery.puppetlabs.net,10.32.119.57"  odcckquiw5m46l9.delivery.puppetlabs.net:  Host key verification failed for odcckquiw5m46l9.delivery.puppetlabs.net: fingerprint 23:d3:c3:60:24:40:08:55:e6:db:16:cb:95:f9:5f:90 is unknown for "odcckquiw5m46l9.delivery.puppetlabs.net,10.32.124.170"  Ran on 3 nodes in 0.07 seconds{code} * Then * I expect to see a non-zero exit code{code}[1] pry(#)> result.exit_code=> 0{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 

Jira (BOLT-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-209 
 
 
 
  Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Environment:
 
 Centos 7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file

2017-11-07 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  BOLT-209 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file  
 
 
 
 
 
 
 
 
 
 
For context on centos7 I get exit code 255 when I attempt this manually 
 
 
 
 
 
 
[root@mvaypj4nxldckoj ~]# ssh r...@mvaypj4nxldckoj.delivery.puppetlabs.net 
 
 
 
 
The authenticity of host 'mvaypj4nxldckoj.delivery.puppetlabs.net (10.32.122.70)' can't be established. 
 
 
 
 
ECDSA key fingerprint is f0:4f:93:08:cf:a7:05:da:7e:ec:f9:a0:e7:b0:4f:47. 
 
 
 
 
Are you sure you want to continue connecting (yes/no)? no
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (BOLT-209) Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file

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

 
 
 
 
 
 
 
 Puppet Task Runner /  BOLT-209 
 
 
 
  Bolt 'command run' exits 0 when '--insecure' flag is not used and there are not match entries in the known_hosts file  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 BOLT 0.7.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2017/11/07 2:44 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
Given  An empty known_hosts file When  
 
 
 
 
 
 
mvaypj4nxldckoj.delivery.puppetlabs.net (centos7-64-1) 14:32:31$ bolt command run 'echo """hello from $(hostname)"""' --nodes mvaypj4nxldckoj.delivery.puppetlabs.net,ucqxte3fgv2l7v7.delivery.puppetlabs.net,odcckquiw5m46l9.delivery.puppetlabs.net -u root -p Qu@lity! 
 
 
 
 
  mvaypj4nxldckoj.delivery.puppetlabs.net: 
 
 
 
 
  

Jira (PUP-7110) Unable to halt Puppet service on Solaris using Puppet

2017-06-12 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert assigned an issue to Zach Reichert 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7110 
 
 
 
  Unable to halt Puppet service on Solaris using Puppet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Assignee:
 
 qa Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-6789) Prefer but don't require capabilities matching the node environment

2016-10-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  PUP-6789 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Prefer but don't require capabilities matching the node environment  
 
 
 
 
 
 
 
 
 
 
Kenn Hussey Susan McNerney I don't think I will have bandwidth to author the automation this sprint. After talking with Alex Dreyer the cases do seem straight forward. I have documented the case in TestRail and created https://tickets.puppetlabs.com/browse/ORCH-1561 to track the automation of this acceptance test. I'll be able to commit to this work in the next Foundational Features sprint.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-6497) CapabilityFinder says a capability couldn't be found if there are multiple versions of it

2016-07-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Zach Reichert 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Severity:
 
 Low 
 
 
 

QA Status:
 
 Reviewed 
 
 
 

QA Contact:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6182) Application declarations don't properly validate component mappings

2016-07-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Zach Reichert 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Severity:
 
 Low 
 
 
 

QA Status:
 
 Reviewed 
 
 
 

QA Contact:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

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

2016-07-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Zach Reichert 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Severity:
 
 Low 
 
 
 

QA Status:
 
 Reviewed 
 
 
 

QA Contact:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6527) hiera_include() fails when compiling an environment catalog

2016-07-28 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6527 
 
 
 
  hiera_include() fails when compiling an environment catalog  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Severity:
 
 Low 
 
 
 

QA Status:
 
 Reviewed 
 
 
 

QA Contact:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6096) Add Acceptance Test for Installing Module with Long Paths with PMT

2016-05-31 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6096 
 
 
 
  Add Acceptance Test for Installing Module with Long Paths with PMT  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Sprint:
 
 CODEMGMT 2016-04-20, CODEMGMT 2016-05-04, CODEMGMT 2016-05-18 (FC) , CODEMGMT 2016-06-15 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6096) Add Acceptance Test for Installing Module with Long Paths with PMT

2016-05-03 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  PUP-6096 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add Acceptance Test for Installing Module with Long Paths with PMT  
 
 
 
 
 
 
 
 
 
 
Blocked by no green run in CI. Otherwise ready for merge.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6096) Add Acceptance Test for Installing Module with Long Paths with PMT

2016-04-27 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6096 
 
 
 
  Add Acceptance Test for Installing Module with Long Paths with PMT  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

QA Status:
 
 Reviewed 
 
 
 

QA Contact:
 
 Zach Reichert 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-6096) Add Acceptance Test for Installing Module with Long Paths with PMT

2016-04-06 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6096 
 
 
 
  Add Acceptance Test for Installing Module with Long Paths with PMT  
 
 
 
 
 
 
 
 
 

Change By:
 
 Zach Reichert 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3386) Puppet Module Gem Dependency Metadata and Installation

2015-07-06 Thread Zach Reichert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Zach Reichert commented on  PUP-3386 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Puppet Module Gem Dependency Metadata and Installation  
 
 
 
 
 
 
 
 
 
 
This feature would go a long way in improving the user experience for installing modules with dependancies. QA has bumped into this on several occasions thinking that we encountered a legitimate bug.  CLOUD-371 CLOUD-366 
There is a possibility that this issue is being masked by BKR-382 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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