[dns_gandi_livedns.sh] Shouldn't store GANDI_LIVEDNS_TOKEN / GANDI_LIVEDNS_KEY into the account conf file

[pini-gh]

The script dnsapi/dns_gandi_livedns.sh shouldn't save GANDI_LIVEDNS_TOKEN nor GANDI_LIVEDNS_KEY into the account configuration file.

Because afterward any new value for the related variable will be ignored, because overridden when sourcing the account.conf file.

To reproduce this behavior:

1. Try to issue a certificate using a wrong Gandi LiveDNS token

$ GANDI_LIVEDNS_TOKEN=whatever acme.sh --issue --server https://acme-v02.api.letsencrypt.org/directory  --dns dns_gandi_livedns --force --domain example.org```

2. At this stage the value of GANDI_LIVEDNS_TOKEN is stored into the account.conf file:

grep TOKEN ~/.acme.sh/account.conf 
GANDI_LIVEDNS_TOKEN='whatever'

3. Try again to issue a certificate using a fixed token

GANDI_LIVEDNS_TOKEN=<token_fixed> acme.sh --issue --server https://acme-v02.api.letsencrypt.org/directory  --dns dns_gandi_livedns --force --domain example.org

4. Unfortunately the current token is overridden when reading the old one from the account.conf which isn't updated:

grep TOKEN ~/.acme.sh/account.conf 
GANDI_LIVEDNS_TOKEN='whatever'

It is impossible to set the token correctly unless it is manually removed from account.conf.

[github-actions]

Please upgrade to the latest code and try again first. Maybe it's already fixed. acme.sh --upgrade If it's still not working, please provide the log with --debug 2, otherwise, nobody can help you.

[pini-gh]

As I understand it there is no need for a log here.