feat: add versioning for request messages #191
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backwards compatible message format. It adds a
version
field to the message, and fallbacks to the existing envelope as a default. This will allow to deploy a worker that supports the current in-flight messages and also a new format. The goal is to eventually phase out the legacy format (the one without aversion
field), and to add a version that doesn't need the S3 keys nor the hydratable attributes (the former is not needed here, but can't yet be removed because of backwards compatibility, the later is an artifact of how the messages are constructed, and it is not important for the worker, it also results in compilation warnings because of the macro use)