[4.4.x] migrate dictionaries event with latest start or stop publish or unpublish state #9152
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 an automatic copy of pull request #9129 done by Mergify.
Issue
https://gravitee.atlassian.net/browse/APIM-6914
Description
Today when we migrate the dictionaries from event to event_latest ( APIM 3.20 to 4.x ) only the last event is migrated. The problem is that if the last event is not a
PUBLISH_DICTIONARY
we can lose a dictionary on gateway side after the migration. For example a dictionary can pass from published and stoped to only stoped.Additional context
Cherry-pick of cae1d15 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally