Skip to content
This repository has been archived by the owner on Jan 4, 2021. It is now read-only.

choria_util has confusing DDL descriptions #359

Closed
ripienaar opened this issue Nov 3, 2017 · 0 comments
Closed

choria_util has confusing DDL descriptions #359

ripienaar opened this issue Nov 3, 2017 · 0 comments

Comments

@ripienaar
Copy link
Collaborator

ripienaar commented Nov 3, 2017

% mco rpc choria_util info -I devco.net --display all
.................
           Choria Version: 0.4.0
           Client Flavour: nats-pure
           Client Options: {"max_reconnect_attempts"=>-1,
                            "reconnect_time_wait"=>1,
                            "dont_randomize_servers"=>true,
                            "name"=>"example.net",
                            "servers"=> [....],
                            "verbose"=>false,
                            "pedantic"=>false,
                            "reconnect"=>true,
                            "ping_interval"=>120,
                            "max_outstanding_pings"=>2,
                            "connect_timeout"=>2}
             Client Stats: {"in_msgs"=>439,
                            "out_msgs"=>37,
                            "in_bytes"=>2108480,
                            "out_bytes"=>44494,
                            "reconnects"=>0}
   Client Library Version: 0.2.4
............

Here it's using Client to mean the NATS client but its confusing what client it means since it also means mco client in our world.

Clarify this

ripienaar added a commit to ripienaar/mcollective-choria that referenced this issue Feb 16, 2018
Clarify that `Client` means the middleware client and not the
mcollective client
ripienaar added a commit that referenced this issue Feb 16, 2018
(#359) improve messaging in the choria_util#info ddl
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant