New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix backup restore #758
Fix backup restore #758
Conversation
1e75357
to
e2bc357
Compare
local tests passed. ready for review @sergioifg94 @Patryk-Stefanski |
Code Climate has analyzed commit 1ab186f and detected 24 issues on this pull request. Here's the issue category breakdown:
View more on Code Climate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes look good to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functionality looks to be restored to previous state. I cannot comment on the new behaviour added though.
I see in the steps to reproduce the example APIManagerBackup
CR is slightly different to that in our official docs but I am assuming based on the comment in the yaml that this is insignificant and in the end is just an arbitrary value right?
what
Fixes: https://issues.redhat.com/browse/THREESCALE-8464
Verification steps
Deploy the operator in cluster wide mode using OLM from this PR branch guide
Prepare external databases
System file storage must be with RWX PVC docs
completed
in the status, the restore process is complete