Ross McFarland
e2cbd955f3
Extract & shim DigitalOceanProvider
2022-01-05 09:47:44 -08:00
Ross McFarland
aae65594f2
Remove explicit use of six
2021-09-17 07:10:07 -07:00
Ross McFarland
9156bdaea0
f-strings for tests pass 1
2021-09-16 16:16:01 -07:00
Ross McFarland
e3b4ac84ed
Merge branch 'master' into fix-caa-records
2021-09-15 18:31:52 -07:00
Brian E Clow
f4caa35caa
Ignoring URLFWD and adjusting test counts for other providers
2021-07-22 14:32:09 -07:00
Ricard Bejarano
2351c406f6
fixed DigitalOcean tests (no need for final dot on CAA records)
2021-04-28 16:26:49 +02:00
Ross McFarland
5e1f653848
Merge remote-tracking branch 'origin/master' into srv_null_records
2021-02-18 07:52:47 -08:00
Mark Tearle
39412924da
Fix handling of NULL SRV records in DigitalOcean provider
2021-02-15 22:24:26 +08:00
Mark Tearle
9d4bd0aaec
Add support for LOC records
2021-02-09 20:41:37 +08:00
Jonathan Leroy
de51e5f531
Add support for DNAME records
2020-10-26 22:18:35 +01:00
Ross McFarland
7958233fcc
Consistently order changes :-/
...
Many providers make their modifications in the order that changes comes. In
python3 this causes things to be inconsistently ordered. That mostly works, but
could result in hidenbugs (e.g. Route53Provider's batching could be completely
different based on the order it sees changes.) Sorting changes consistently
is a good thing and it shouldn't hurt situations where providers are already
doing their own ordering. All-in-all more consistent is better and we have to be
explicit with python 3.
2019-10-07 09:17:48 -07:00
Ross McFarland
f252aa3b98
Merge remote-tracking branch 'origin/master' into python3-start
2019-10-05 07:20:47 -07:00
Ross McFarland
a9d0eef3ba
Lots of text_type
2019-07-29 08:37:47 -07:00
Kitten King
daa6fecc9b
Fix Typos
2019-07-20 06:31:05 +00:00
Ross McFarland
88ff1729ab
Implement populate exists for DigitalOceanProvider
2018-01-21 14:55:53 -08:00
Adam Smith
feec4a6821
Add DigitalOcean provider
2017-11-12 23:50:52 -08:00
