Take into account multiple ways of redis persistence and ensure import is being done on the running UI pod. #107
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.
Trello Ticket: https://trello.com/c/w6Pj1IpF/4549-look-into-this-selfhosted-issues-while-migration-if-this-is-something-we-need-to-fix
Redis has multiple ways of persisting data on FS: https://redis.io/docs/latest/operate/oss_and_stack/management/persistence/
It can be a single .aof file or a combination of RDB+AOF. To ensure that we properly cleanup data for both cases, I left both commands in, but with the
-f
flag to ensure that there are no errors if either path doesn't exist.NOTE: not sure about adding
sudo
. It was needed for these commands in my case. Should we leave that in or rather remove it and the user must figure that out?Regarding the second issue in the Trello ticket, we can see that multiple pod names have been assigned to the
UI_POD
variable. I presume that other ones were just leftover pods of failed deployments. I added a filter to the command to ensure that only the running UI pod is assigned.