Jira (BOLT-1127) Bolt should echo port if custom SSH port is used
Title: Message Title Dylan Ratcliffe commented on BOLT-1127 Re: Bolt should echo port if custom SSH port is used This would also be good for vagrant hosts which are much the same, all 127.0.0.1 with different ports Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295971.1550016479000.10932.1562778900133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1127) Bolt should echo port if custom SSH port is used
Title: Message Title David Alexander commented on BOLT-1127 Re: Bolt should echo port if custom SSH port is used If showing the name is too difficult Lucy Wyman just show the port as per my first example - at least this will allow easy differentiation between results. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295971.1550016479000.29331.1559265060066%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1127) Bolt should echo port if custom SSH port is used
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1127
Bolt should echo port if custom SSH port is used
Change By:
Lucy Wyman
When connecting to the same IP address with Bolt, the output appears as follows:{{[puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770}}{{Started on 127.0.0.1...}}{{Started on 127.0.0.1...}}{{Started on 127.0.0.1...}}{{Finished on 127.0.0.1:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on 127.0.0.1:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on 127.0.0.1:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Successful on 3 nodes: root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770}}{{Ran on 3 nodes in 0.24 seconds}} There is no way to tell which node is which. This is mildly problematic with Docker containers, but is very problematic where PAT is being used between networks and multiple nodes are being targeted. Ideally, the output would appear as this: {{[puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770}}{{Started on 127.0.0.1...}}{{Started on 127.0.0.1...}}{{Started on 127.0.0.1...}}{{Finished on 127.0.0.1:32768:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on 127.0.0.1:32769:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on 127.0.0.1:32770:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Successful on 3 nodes: root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770}}{{Ran on 3 nodes in 0.24 seconds}} Alternatively, it would be good to have a syntax switch in the --nodes parameter such that an alias could be passed - e.g. {{[puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes root@127.0.0.1:32768\{node1},root@127.0.0.1:32769\{node2},root@127.0.0.1:32770\{node3}}}{{Started on node1...}}{{Started on node2...}}{{Started on node3...}}{{Finished on node1:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on node2:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Finished on node3:}}{{ STDOUT:}}{{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}}{{Successful on 3 nodes: root@127.0.0.1:32768\{node1},root@127.0.0.1:32769\{node2},root@127.0.0.1:32770\{node3}}}{{Ran on 3 nodes in 0.24 seconds}} The real issue here is that 'uri' may not be displayable, so how can we compute a display name from the uri if the user doesn't specify a 'name'? If you've specified a name we can use that as the display name.Plan authors can print the display name with {{target.to_s}}How can we ship this in a way that's safe for users on Inventory v1 to use?
Jira (BOLT-1127) Bolt should echo port if custom SSH port is used
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1127 Bolt should echo port if custom SSH port is used Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1127) Bolt should echo port if custom SSH port is used
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1127 Bolt should echo port if custom SSH port is used Change By: Nick Lewis Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1127) Bolt should echo port if custom SSH port is used
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1127 Bolt should echo port if custom SSH port is used Change By: Nick Lewis Team: Bolt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1127) Bolt should echo port if custom SSH port is used
Title: Message Title
David Alexander created an issue
Puppet Task Runner / BOLT-1127
Bolt should echo port if custom SSH port is used
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/02/12 4:07 PM
Priority:
Normal
Reporter:
David Alexander
When connecting to the same IP address with Bolt, the output appears as follows: [puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770 Started on 127.0.0.1... Started on 127.0.0.1... Started on 127.0.0.1... Finished on 127.0.0.1: {{ STDOUT:}} {{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}} Finished on 127.0.0.1: {{ STDOUT:}} {{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}} Finished on 127.0.0.1: {{ STDOUT:}} {{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}} Successful on 3 nodes: root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770 Ran on 3 nodes in 0.24 seconds There is no way to tell which node is which. This is mildly problematic with Docker containers, but is very problematic where PAT is being used between networks and multiple nodes are being targeted. Ideally, the output would appear as this: [puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770 Started on 127.0.0.1... Started on 127.0.0.1... Started on 127.0.0.1... Finished on 127.0.0.1:32768: {{ STDOUT:}} {{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}} Finished on 127.0.0.1:32769: {{ STDOUT:}} {{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}} Finished on 127.0.0.1:32770: {{ STDOUT:}} {{ 00:02:58 up 3:56, 0 users, load average: 0.00, 0.16, 0.40}} Successful on 3 nodes: root@127.0.0.1:32768,root@127.0.0.1:32769,root@127.0.0.1:32770 Ran on 3 nodes in 0.24 seconds Alternatively, it would be good to have a syntax switch in the --nodes parameter such that an alias could be passed - e.g. [puppet@da-rhel-wks-01 ~]$ bolt command run uptime --nodes root@127.0.0.1:32768{node1},root@127.0.0.1:32769{node2},root@127.0.0.1:32770{node3} Started on node1... Started on node2... Started on node3... Finished on node1: {{ STDOUT:}} {{ 00:02:58 up 3:56, 0 users, load
