v2.4.0

Significant Changes

• Persisting actions on uplink shutdown allows users to temporarily halt uplink and restart it, without losing out on information with regards to the action that is in execution and hence allowing the user to bring back up both uplink and the external action handler, continuing action execution as if nothing had happened. This is possible because uplink stores action information along with all on-disk persistence files in the same directory, the diff for changes to support this is provided below:

+ persistence_path = "/path/to/dir"

[streams.stream_name]
topic = "/stream/topic"
buf_size = 100
- persistence = { path = "/path/to/dir", max_file_count = 3, max_file_size = 10485760 }
+ persistence = { max_file_count = 3, max_file_size = 10485760 }

What's Changed

• refactor: use VecDeque for readability by @de-sh in #227
• fix: update backup-deserializer to support uplink v2.3 by @de-sh in #233
• feat: current action persistence on abrupt shutdowns by @de-sh in #216
• feat: log processes by unit name in journalctl by @de-sh in #225

Full Changelog: v2.3.0...v2.4.0