gistfile1.txt

$ mco choria show_config
Active Choria configuration:

The active configuration used in Choria comes from using Puppet AIO defaults, querying SRV
records and reading configuration files.  The below information shows the completely resolved
configuration that will be used when running MCollective commands

MCollective related:

    MCollective Version: 2.8.9
     Client Config File: /etc/puppetlabs/mcollective/client.cfg
     Active Config File: /etc/puppetlabs/mcollective/client.cfg
      Plugin Config Dir: /etc/puppetlabs/mcollective/plugin.d
      Using SRV Records: true
              Federated: false
             SRV Domain: <SNIP>.com
     Middleware Servers: puppet:42222

Puppet related:

       Puppet Server: puppet:8140
     PuppetCA Server: puppet:8140
     PuppetDB Server: puppet:8140
      Facter Command: /opt/puppetlabs/bin/facter
       Facter Domain: <SNIP>.com

SSL setup:

     Valid SSL Setup: no run 'mco choria request_cert'
            Certname: <USER>.mcollective
       SSL Directory: /home/local/<USER>/.puppetlabs/etc/puppet/ssl (found)
  Client Public Cert: /home/local/<USER>/.puppetlabs/etc/puppet/ssl/certs/<USER>.mcollective.pem (absent)
  Client Private Key: /home/local/<USER>/.puppetlabs/etc/puppet/ssl/private_keys/<USER>.mcollective.pem (absent)
             CA Path: /home/local/<USER>/.puppetlabs/etc/puppet/ssl/certs/ca.pem (absent)
            CSR Path: /home/local/<USER>/.puppetlabs/etc/puppet/ssl/certificate_requests/<USER>.mcollective.pem (absent)

Active Choria configuration settings as found in configuration files:

  No custom Choria settings found in your configuration files