API Changelog 4.73.0 #251
Merged
API Changelog 4.73.0 #251
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
yoshizzle
requested changes
Aug 24, 2020
Collaborator
yoshizzle
left a comment
yoshizzle
left a comment
There was a problem hiding this comment.
I'd maybe also add this: https://bits.linode.com/LinodeAPI/apinext/pull/2839/files#diff-4ac32a78649ca5bdd8e0ba38b7006a1eR33
|
|
||
| ### Fixed | ||
| - A bug was fixed that would result in a 500 error when filtering domain records by a non-existent tag. This will now return an empty 200 respone. | ||
| - Previously, NS and CNAME records could be created for eachother, resulting in errors. If this is attempted now, the record creation will fail with a "Record conflict" message. |
Collaborator
There was a problem hiding this comment.
"each other" (two words)
alsaihn
reviewed
Aug 24, 2020
Contributor
alsaihn
left a comment
alsaihn
left a comment
There was a problem hiding this comment.
Small clarification for where the NS/CNAME error previously showed up.
|
|
||
| ### Fixed | ||
| - A bug was fixed that would result in a 500 error when filtering domain records by a non-existent tag. This will now return a 200 response with an empty pagination result. | ||
| - Previously, NS and CNAME records could be created for each other, resulting in errors. If this is attempted now, the record creation will fail with a "Record conflict" message. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Previously, NS and CNAME records could be created for each other, resulting in errors. If this is attempted now, the record creation will fail with a "Record conflict" message. | |
| - Previously, NS and CNAME records could be created for each other, resulting in errors when the zone file gets rendered. If this is attempted now, the record creation will fail with a "Record conflict" message. |
alsaihn
approved these changes
Aug 24, 2020
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.
No description provided.