Adding a new exception code/message, testing backup exceptions #692
Conversation
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.
The backup client bad responses have different XML responses than the others.
<ns0:Status xmlns:ns0="http://oec.api.opsource.net/schemas/general">
ns0:operationEnable Backup for Server/ns0:operation
ns0:resultERROR/ns0:result
ns0:resultDetailCloud backup for this server is already enabled or being enabled (state: NORMAL)./ns0:resultDetail
ns0:resultCodeREASON_550/ns0:resultCode
/ns0:Status
I added in handling for this and making it easier to create new bad xml elements in case there are more later on.
Added tests to test the bad handling in the backup client