* Re: Fwd: Add support for godaddy.com
[not found] <CAHJDaaZUtkz4ocTvPRNxb=nvGgE-nhAY5DsNOMiuDOFn1Ti6Pw@mail.gmail.com>
@ 2023-03-15 12:19 ` Stefan Schantl
2023-03-16 7:46 ` Michael Tremer
0 siblings, 1 reply; 2+ messages in thread
From: Stefan Schantl @ 2023-03-15 12:19 UTC (permalink / raw)
To: ddns
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
Hello Costas,
thanks for sending your patch here and once again for sending the same
patch as a pull request on github.
I really don't know, why your first mail did not appear in my inbox,
nor got displayed on our patchwork infrastructure.
After a quick code review and some basic testing with invalid data,
everything seems to work and I finally merged your patchset.
In addition to this I tagged a new version of ddns, which will be part
of one of the next upcomming Core updates.
Best regards,
-Stefan
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Add support for godaddy.com
2023-03-15 12:19 ` Fwd: Add support for godaddy.com Stefan Schantl
@ 2023-03-16 7:46 ` Michael Tremer
0 siblings, 0 replies; 2+ messages in thread
From: Michael Tremer @ 2023-03-16 7:46 UTC (permalink / raw)
To: ddns
[-- Attachment #1: Type: text/plain, Size: 2247 bytes --]
Hello Costas,
I would like to drop a couple of comments about this patch:
It uses f-strings which we do not use at all in ddns and so I wouldn’t want to start now.
The newly added provider class does not make use of the send_request method (https://git.ipfire.org/?p=ddns.git;a=blob;f=src/ddns/system.py;h=48c9a8f88fdde2b922cb6548e450c9a1407851fb;hb=HEAD#l124) which we use to log the request, configure extra settings like an upstream proxy, etc. Just calling urlopen() is not sufficient.
The TTL is set to 600. I cannot find anything about this in the upstream documentation, but that seems to be an eternity compared to the other providers where the TTL is at maximum 60s. If there is a way to choose, then we should use a lower value here.
This does not support IPv6 at all. The A record is hardcoded although GoDaddy supports AAAA records, too.
Then it is not being implemented that a record can be deleted even though the API supports it: https://developer.godaddy.com/doc/endpoint/domains#/v1/recordDeleteTypeName
Then the error handling is incorrect as ddns handles all mentioned error codes automatically. It is not necessary to perform manual stuff here. So this is just dead code that would never be reached when using send_request().
I am very grateful for your patch submission but it cannot be merged like this as it introduces some major problems. Please submit an improved patch.
Best,
-Michael
> On 15 Mar 2023, at 12:19, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
>
> Hello Costas,
>
> thanks for sending your patch here and once again for sending the same
> patch as a pull request on github.
>
> I really don't know, why your first mail did not appear in my inbox,
> nor got displayed on our patchwork infrastructure.
>
> After a quick code review and some basic testing with invalid data,
> everything seems to work and I finally merged your patchset.
>
> In addition to this I tagged a new version of ddns, which will be part
> of one of the next upcomming Core updates.
>
> Best regards,
>
> -Stefan
>
> _______________________________________________
> ddns mailing list
> ddns(a)lists.ipfire.org
> https://lists.ipfire.org/mailman/listinfo/ddns
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-03-16 7:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CAHJDaaZUtkz4ocTvPRNxb=nvGgE-nhAY5DsNOMiuDOFn1Ti6Pw@mail.gmail.com>
2023-03-15 12:19 ` Fwd: Add support for godaddy.com Stefan Schantl
2023-03-16 7:46 ` Michael Tremer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox