Add deprecation to DNS Records API - Remove eligible zones for custom nameservers endpoint #18840
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
matilde-cf
force-pushed
the
matilde/eligible-zones-deprecation
branch
2 times, most recently
from
e2f6c11 to
864952f
Compare
… nameservers endpoint
matilde-cf
force-pushed
the
matilde/eligible-zones-deprecation
branch
from
864952f to
3408a24
Compare
ghost
approved these changes
Dec 18, 2024
patriciasantaana
approved these changes
Dec 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Summary
This add a DNS records API deprecation to remove the
GET /accounts/:account_id/custom_ns/availabilityendpoint.It is now possible for users to add custom nameservers that are not part of a zone managed within their account. As a result, an endpoint to check for eligible zones is no longer relevant.
Documentation checklist
cc @hannes-cf