Updated to support latest Cloudflare Registrar responses #719
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.
Description
It appears that the /registrar API has been through some improvements since this module was written. I want to support cloudflare as a registrar in dnscontrol but the existing code doesn't return nameservers and other data. The publicly documented API does not match response being returned from the API at this time.
e.g.
This is the
accounts/[id]/registrar/domain
output for a domain I currently control (I've censored the domain, but everything else is real)A bunch of things from the documented API are missing (e.g. registrant_contact, id, transfer_in) and a ton of new (and useful) fields have been added. So the existing documentation doesn't match the current implementation.
Has your change been tested?
I added new tests and have used this with my personal account. I was unable to test transfers as they are no longer documented on the API page and I don't have a domain to transfer in at the moment.
Checklist: