Release v15.29.6
Summary
Fixes MongoDB direct connection precedence so ?directConnection=true in connection strings is honored across Chronicle MongoDB storage paths, and updates Docker get-started guidance for single-node replica sets usable from both host tools and containers.
Added
- Added Storage.MongoDB specs covering
directConnection=truebehavior forDatabase, read-model database creation,EventStoreDatabase, andEventStoreNamespaceDatabase.
Changed
- Updated the Docker get-started MongoDB Compose example to use
Cratis__Chronicle__Storage__ConnectionDetails=mongodb://mongodb:27017/?directConnection=true. - Updated replica set initialization guidance to advertise
localhost:27017and documented why this works for host access and Chronicle-in-container access. - Added guidance to reset volumes (
docker compose down -v) when reinitializing a replica set previously created with a different host.
Fixed
- Fixed MongoDB storage configuration so default
MongoDBOptions.DirectConnectionno longer overridesdirectConnection=truesupplied in the MongoDB connection string.
Removed
- None.
Security
- None.
Deprecated
- None.