Google Cloud DNS #378
Closed
Google Cloud DNS #378
Conversation
This file contains hidden or 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
added 4 commits
October 19, 2014 22:44
If the status code for a call to the Google Cloud's API is 409 (CONFLICT), and the code of the error is 'alreadyExists', consider the resource as already existing and create the correct error.
The default can't be `None' since we're calling `int' on the value of ttl.
|
@franckcuny - thanks! |
|
Merged into trunk. Thanks. |
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.
This CL fix a couple of bugs for the Google Cloud DNS' API, and handle the error code 'alreadyExists' as a 'ResourceExistsError'.
cc @erjohnso