Russ
08/20/2025, 5:20 PMThis is the active Choria configuration as resolved from
its configuration files and defaults.
Details about configuration items can be seen by passing an
extra argument that will act as a search term against known
configuration items.
Configuration Files:
User Config: /etc/choria/client.conf
Loaded Files: /etc/choria/client.conf
/etc/choria/plugin.d/actionpolicy.cfg
/etc/choria/plugin.d/choria.cfg
Security Configuration:
Security Provider: Puppet
Valid Security: yes
Caller ID: choria=choria.mcollective
Certname: choria.mcollective
Connectivity:
Main Collective: mcollective
Collectives: mcollective
Service Registry: disabled
SRV Domain: <redacted>
Facter Command: /opt/puppetlabs/bin/facter
Facter Domain: <redacted>
Facter FQDN: choria-i-003e2b94acf5c199b.<redacted>
PuppetDB Server: https://<redacted>:8081
Choria Brokers: <nats://choria>.<redacted>:4222
Federation Brokers: <nats://choria>.<redacted>:4222
Collectives: <redacted>
Loaded Configuration:
These settings were specifically loaded from configuration
files and do not include any defaults.
collectives: mcollective
connection_timeout: 3
connector: nats
identity: choria.<redacted>
libdir: /opt/puppetlabs/mcollective/plugins
logger_type: console
loglevel: warn
main_collective: mcollective
plugin.actionpolicy.allow_unconfigured: 0
plugin.actionpolicy.enable_default: 0
plugin.choria.federation.cluster: <redacted>
plugin.choria.federation.collectives: <redacted>
plugin.choria.srv_domain: <redacted>
plugin.choria.use_srv: true
securityprovider: choria