Releases
v0.23.0
Enhancements
Improve DDL data types for core DDL files
Allow the Choria Server to run in an Services-Only mode
Support Websockets for connectivity from Leafnodes and Choria Server to Choria Broker, also Go clients
Initial implementation of the choria_registry
service agent
Adds a choria login
command that supports delegating to choria-login
in PATH
Improve sorting of choria inventory
columns
Fail when a client cannot determine its identity
Allow the default collective to be set at compile time
Allow the default client suffix to be set at compile time (eg. rip.mcollective user id)
Allow a random sleep at the start of schedules for the Schedule watcher
Rate limit fast transitions in autonomous agents
Use default client-like resolution to find brokers in the JetStream adapter when no urls are given
Introduce Choria Submission to allow messages to be placed into Streams via Choria Server
Support PKCS8 containers
Introduce Choria Governor for network wide concurrency control
Support Governors in the Exec Autonomous Agent watcher
Additional Prometheus statistics for Choria Streams
Add a Autonomous Agent level data store, allow Exec Watchers to gather and store data in a Auto Agent
Allow Exec Watchers to access node facts
Add a Choria Key-Value Store accessible using choria kv
and a new kv
Autonomous Agent Watcher
Expose kv
data to the Autonomous Agent data system
Support templates in Exec Watcher cmd
, env
and governor
Export certificate expiry time in Choria status files, support checking from CLI and Scout
Support Asynchronous Request mode in generated Go clients
Extend the RPC Reply structure to include what action produced the data
Use correct Choria reply subjects when interacting with the Streams API
Improve the broker shutdown process to cleanly shut down Choria Streams
Allow compiled-in Go agents to access the Submission system
Rename the jetstream
adapter to choria_streams
Disable RPC Auth during provisioning mode
Support entering provisioning mode when the supplied server.conf
does not exist
Generated clients can accept a Choria Framework, avoiding config loading etc
Include the time a RPC Reply was generated in the reply
Include the Public Key in the CSR reply, add data type hints to the provisioner DDL and update client
Support receiving private keys from the provisioner, protected using Curve 25519 ECDH shared secrets
Correctly enter provisioning with a configuration file and without a Puppet installation
Ensure SSL Cache is created if needed during provisioning
Support sorting choria req
output by identity using --sort
Enable the choria_provision
agent when provisioning is supported
Support Debian 11
Bug Fixes
Fix setting workers and expr filter on generated clients
Ensure no responses list and unexpected responses list always prints, capped to 200 nodes
You can’t perform that action at this time.