Fixed conflicts with px-backup master merge #192
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sgajawada-px
requested review from
prashanthpx,
siva-portworx,
lalat-das and
px-kesavan
|
@sgajawada-px Please do a test of the px-backup i.e. backup & restore scenario working with this vendoring of px-backup-api.... If that is through lets merge this post that test |
|
Not needed any more |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
To resolve the build issue when the px-backup-api master vendor into the px-backup.
Which issue(s) this PR fixes (optional)
Closes #
Special notes for your reviewer: