Update LiveDNS endpoint and the docs URL

[Themimitoof]

Since April 2020 we (Gandi) have deprecated the old LiveDNS endpoint in favor of the new one that is part of our public API project.

This PR update the endpoint but also the link to the new documentation.

cc @grigouze @romuald

[romuald]

Nicely spotted, however this is not enough ^^

The authentication mechanism did change between the 2 endpoints:
you need to authenticate on api.gandi.net with an Authorization: apikey XXXX header instead of X-API-Key: XXXX

[Themimitoof]

Thanks @romuald for the review, I just pushed a commit to update this part 😉.

[obynio]

@Themimitoof Thank you for your PR, I'll take a look to ensure the endpoints are the same before making the switch. However your new API is still shown as being in beta and this plugin is being used for production systems. Do you believe the new API is mature enough to be used in production ?

The documentation explicitly states Please note that this API is currently in BETA testing, so care should be taken when used in production

[obynio]

At a first glance, it appears the https://api.gandi.net/v5/livedns/domains endpoint has changed and the attribute zone_records_href from the previous API has vanished.

Unfortunately for some silly reason of mine I was using this attribute here and there to make my requests. Could you replace the domain.ZoneRecordsHref currently used to make requests by domain.DomainRecordsHref ?

[obynio]

I see that the when using the domain_records_href instead of the zone_records_href attribute we can submit both relative and absolute names for this endpoint.

That's good, it means I we may finally ditch that hack I'm not so proud of and use either wiki.gconfs.fr. and wiki to manipulate zones. Can you make this change also ?

[obynio]

I think I've listed everything that is needed to make the plugin works with the new endpoint.
Feel free to drop me a line if you need help.

[obynio]

@Themimitoof any news on this ?

[Themimitoof]

Hello @obynio, unfortunately, I don't have enough bandwidth lately. I hope to be able to work on it this weekend.

Have you a test procedure to try to test locally before requesting you a new review?

[obynio]

We are lucky enough to have a very easy way to spin out a dev environment using xcaddy. It allows you to build and run caddy with your development plugin in two commands. https://github.com/caddyserver/xcaddy#for-plugin-development

You can configure a simple Caddyfile like this one. Replace the domain by one you own.

pad.leon.re {
	tls {
		dns gandi {env.GANDI_API_TOKEN}
	}
	respond "Hello, world!"
}

Then in the directory of the plugin you're working on run xcaddy

$ xcaddy run --config Caddyfile

Then xcaddy will fetch the caddy sources, compile it with your plugin and run immediately.
If you need help feel free to reach out to me 👍

[Themimitoof]

In fact no we don't have a strange regexp in the api but this is a normal behavior.

When you specify this record in your BIND zone:

hello.skusku.pw    IN   A    3600    127.0.0.1

The record will be available in hello.skusku.pw.skusku.pw because we wasn't added the point to mark the end of the FQDN (also named absolute record in the RFC1035 (Domain names that end in a dot are called
absolute, and are taken as complete).

I think you already know that, just as reminder ;)

[Themimitoof]

Sharing ids are not an authentication mechanism. In fact a sharing id is the identifier of an organization.

[Themimitoof]

Hello @obynio 👋

Here is my modifications to make the module working this the new LiveDNS API. I tested a couple of times and adding/append and deleting records works fine.

It was the first time I played with Go, it was fun to understand how the module works and to contribute to it 😅

The documentation explicitly states Please note that this API is currently in BETA testing, so care should be taken when used in production

Soon it will disappear, don't worry about that 😉