> largely because I could imagine the tags being used in a way the example doesn't cover: DC/AZ/Region tags.

I'll add this feature to the roadmap then :)

> I don't know that a full parser for Boolean logic is necessary - even having a complimentary `-T` option that takes mandatory tag names might be enough.

I truly dislike command lines with hundreds of arguments. IMHO, A boolean logic would be clearer on the intent than a combination of -t -T -not-T etc...

> so it's multiple background SSH processes.

I'm not sure yet if parallelization should be the default or not. Also I've not yet learned Tokio and Async programming in Rust :P

> some way to have per-host data sent

Yes, just like Ansible evaluates very variable per host. At the moment you can do it manually:

  res=$(tricorder -i inventory -- echo "available")
  host_ids=$(echo $res | jq "some jq black magic")

  for host_id in $host_ids
  do
    tricorder -i inventory -H $host_id -- echo "specific data sent to $host_id"
  done

Maybe i'll make use of the `tinytemplate` crate and add a -D option for data that would be similar to the inventory (TOML static file or program/script outputting JSON).

I'm not sure yet on how it should look.

I mean to keep tricorder KISS so it can be integrated easily in a bash script as a standalone command, and not a full-on folder structure like ansible playbooks.