Skip to content

Release v2.1.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 03 Nov 23:14
v2.1.0
32c62fa
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choreography can now apply one-time data changes when a release starts, and it does so without taking the old release down. A rolling upgrade no longer needs the replica set scaled to zero and back up: new pods start while old pods keep serving.

Added

  • Startup patching: implement ICanApplyPatch and the patch is discovered, ordered by version and applied once per store before the silo takes work.
  • A cluster-wide patch manager grain that is safe in mixed-release clusters. When a newer host asks an older manager, the manager moves to the newer host before patching, and an older host never patches a store a newer host already patched.
  • Resilient startup during rollouts: a lost silo, a rejected message or a patch that outlasts the grain response timeout is retried with back-off instead of failing the start, bounded by PatchingOptions.MaxWait (15 minutes by default) and reported as PatchingDidNotComplete.
  • Patch storage for in-memory, MongoDB and SQL (SQL Server and PostgreSQL) stores, with the SQL tables created by Choreography's own migrations.
  • AddCratisChoreographyPatching and CratisChoreographyOptions.ConfigurePatching to turn patching on and tune it.
  • Complete documentation, reorganized by feature area, with a patching section and troubleshooting entries.
Assets 2
Loading