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.
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}
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.
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.
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.
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.
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.