Skip to content

Direct `stream_name` configurability! (Removing `app_name` configs)
Compare
Choose a tag to compare
@smudge smudge released this 27 Oct 21:09
· 10 commits to master since this release
v4.0.0
0cb1f01
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This release replaces default_app_name, journaled_app_name, and other app_name usage with default_stream_name, journaled_stream_name, and stream_name (respectively). It also moves off of an ENV-vars-by-default approach for stream configuration, to more of a BYO-ENV-vars strategy (where you can still reference the old ENV vars if you want).

Naturally, this prompts a major version bump to 4.0, and upgrade instructions have been added the README.

Other Information

  • Worth noting, stream_name is now baked-into the Journaled::DeliveryJob handlers. This means that jobs will use the stream names that the events were configured to use at the time they were enqueued.

  • The Journaled::Delivery "performable" class has been removed. (It was succeeded by the Journaled::DeliveryJob ActiveJob in version 3.0.) This means that anyone upgrading directly from 2.5.0 or below to 4.0 (this new version) will see errors if they have any jobs actively queued. A recommendation has been added to the README to upgrade one major version at a time, so 2.x -> 3.x -> 4.x would be the safest path.

Assets 2
Loading