-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for changing TTL on DigitalOcean domain records. #14805
Conversation
Thanks for this - unfortunately, this doesn't pass the tests:
Can you take a look? Paul |
@stack72 Looks like that is actually an error on the DO API side. The Droplet creation events are failing. So probably best to rerun when the status page is green: http://status.digitalocean.com/ |
The DO status page is back to green, and I just successfully ran the acceptance tests. |
Thanks for letting us know - apologies for the delayed response here. Would it be possible to fix the merge conflicts? Once this is done we can progress with this :) Thanks! |
29d8101
to
c7299b8
Compare
Well, it's a much smaller patch now. 😄 |
This LGTM now :) Thanks for taking care of this |
@andrewsomething thanks a lot for this change! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
The DO API was extended to support configuring the TTL value for individual domain records. See:
https://developers.digitalocean.com/documentation/changelog/api-v2/configurable-ttl-for-domain-records/
This PR adds support for that as well as updating the vendorized copy of godo. That required a few changes:
https://developers.digitalocean.com/documentation/changelog/api-v2/deprecating-update-tag/
Fixes: #12631