Jira (BOLT-1398) I want to see what nodes are in an inventory group

0 views
Skip to first unread message

Lucy Wyman (JIRA)

unread,
Jun 14, 2019, 7:01:03 PM6/14/19
to puppe...@googlegroups.com
Lucy Wyman created an issue
 
Puppet Task Runner / Task BOLT-1398
I want to see what nodes are in an inventory group
Issue Type: Task Task
Assignee: Unassigned
Created: 2019/06/14 4:00 PM
Priority: Normal Normal
Reporter: Lucy Wyman

Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.

We should find what use cases current users have around displaying inventory.

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

Alex Dreyer (JIRA)

unread,
Jun 18, 2019, 12:41:02 PM6/18/19
to puppe...@googlegroups.com
Alex Dreyer updated an issue
Change By: Alex Dreyer
Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.

We should find what use cases current users have around displaying inventory.



A workaround for now is to use a plan that returns the targets
{noformat}
plan resolve_targets( TargetSpec $nodes) {
  return(get_targets($nodes))
}
{noformat}

Lucy Wyman (JIRA)

unread,
Jun 25, 2019, 12:52:04 PM6/25/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
Change By: Lucy Wyman
Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.

We should find what use cases current users have around displaying inventory.


A workaround for now is to use a plan that returns the targets
{noformat}
plan resolve_targets( TargetSpec $nodes) {
  return(get_targets($nodes))
}
{noformat}


This should be a new command {{bolt inventory show <some targetting option>}} where some targetting option supports similar options to {{bolt * run}} (ie. {{--rerun}}, {{--targets}}, etc.). The output should be support both human output (printed list of names and maybe the total number of nodes), and a JSON array names for the json output.

Lucy Wyman (JIRA)

unread,
Jun 25, 2019, 12:53:02 PM6/25/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.

We should find what use cases current users have around displaying inventory.

A workaround for now is to use a plan that returns the targets
{noformat}
plan resolve_targets( TargetSpec $nodes) {
  return(get_targets($nodes))
}
{noformat}

Solution:
This should be a new command {{bolt inventory show <some targetting option>}} where some targetting option supports similar options to {{bolt * run}} (ie. {{--rerun}}, {{--targets}}, etc.). The output should be support both human output (printed list of names and maybe the total number of nodes), and a JSON array names for the json output.

Lucy Wyman (JIRA)

unread,
Jun 25, 2019, 12:54:04 PM6/25/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.

We should find what use cases current users have around displaying inventory.

A workaround for now is to use a plan that returns the targets
{noformat}
plan resolve_targets( TargetSpec $nodes) {
  return(get_targets($nodes))
}
{noformat}

Solution:
This should be a new command {{bolt inventory show <some targetting option>}} where some targetting option supports similar options to {{bolt * run}} (ie. {{--rerun}}, {{--targets}}, etc.). The output should be support both human output (printed list of names on newlines and maybe the total number of nodes), and a JSON array names for the json output.

Lucy Wyman (JIRA)

unread,
Jun 25, 2019, 12:54:04 PM6/25/19
to puppe...@googlegroups.com

Lucy Wyman (JIRA)

unread,
Jun 25, 2019, 12:55:03 PM6/25/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
Change By: Lucy Wyman
Sprint: Bolt Ready for Grooming Kanban

Tom Beech (JIRA)

unread,
Jun 27, 2019, 3:07:03 PM6/27/19
to puppe...@googlegroups.com

Lucy Wyman (JIRA)

unread,
Jun 28, 2019, 5:09:03 PM6/28/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
Change By: Lucy Wyman
Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.

We should find what use cases current users have around displaying inventory.

A workaround for now is to use a plan that returns the targets
{noformat}
plan resolve_targets( TargetSpec $nodes) {
  return(get_targets($nodes))
}
{noformat}

Solution:
This should be a new command {{bolt inventory show <some targetting option>}} where some targetting option supports similar options to {{bolt * run}} (ie. {{--rerun}}, {{--targets}}, etc.). The output should be support both human output (printed list of names on newlines and the total number of nodes), and a JSON array names for the json output.
This should just return a list of target names for targets which match the targetting option and are also in the inventory.

Lucy Wyman (JIRA)

unread,
Jun 28, 2019, 5:10:02 PM6/28/19
to puppe...@googlegroups.com
Lucy Wyman updated an issue
Even before inventory was dynamic users wanted to be able to display which nodes were in a group in an inventory https://github.com/puppetlabs/bolt/issues/537. Now that inventory can be dynamic this seems even more useful.

We should find what use cases current users have around displaying inventory.

A workaround for now is to use a plan that returns the targets
{noformat}
plan resolve_targets( TargetSpec $nodes) {
  return(get_targets($nodes))
}
{noformat}

Solution:
This should be a new command {{bolt inventory show <some targetting option>}} where some targetting option supports similar options to {{bolt * run}} (ie. {{--rerun}}, {{--targets}}, etc.). The output should be support both human output (printed list of names on newlines and the total number of nodes), and a JSON array names for the json output.
This should just return a list of target names for targets which match the targetting option and are also in the inventory.

{{bolt inventory show}} without any other options should error.

Lucy Wyman (JIRA)

unread,
Jul 3, 2019, 7:28:03 AM7/3/19
to puppe...@googlegroups.com

Michelle Fredette (JIRA)

unread,
Jul 10, 2019, 3:32:02 PM7/10/19
to puppe...@googlegroups.com

Michelle Fredette (JIRA)

unread,
Jul 10, 2019, 3:32:04 PM7/10/19
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages