Add message retention options to subscriber action #42
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.
Add configurable option to add retention policy for the subscribed message. Specifically configure whether a message should be cleared after first read, or latch the message until the message is replaced. This is useful for low frequency/only on change state type topics if interested in what last state is.
For backwards compatibility set
READ_ONCE
as default option.Have used a template parameter due to the
providedBasicPorts
function being static, and therefore not able to access virtual members, and the configuration parameter needing to be the same in thetick
function.