Have TGB handler reset checkpoint properly on cleanUp(). #4355
+5
−6
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.
Issue
#4343
Description
The current check pointing logic returns old check point = new check point = "". This means, when clean up is invoked for a now existent service, the checkpoint doesn't get updated due to this check. This leads to the old checkpoint being persisted in the TGB, despite the target group being updated. In the users case, the endpoint composition didn't change therefore when the service backend was corrected our TGB handler didn't re-register the targets.
The fix is quite simple, instead of setting both checkpoints to empty, we return the oldCheckPoint as the actual checkpoint, and the new checkpoint as "". This was the checkpoint is properly updated and the handler will re-register the targets when the service is fixed.
Checklist
README.md
, or thedocs
directory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯