gandi setup output

[Marc-marc-marc]

in README.md, the current output is

$ gandi setup

API Key: x134z5x4c5c # copy-paste your api key
Environment [production] : # press enter for Production, the default
SSH key [~/.ssh/id_rsa.pub] : # your SSH public key for hosting instances and servers

my output

$ uname -a
Linux localhost.localdomain 3.10.0-957.27.2.el7.x86_64 #1 SMP Mon Jul 29 17:46:05 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$ gandi --version
Gandi CLI 1.5
$ gandi setup
Api key (xmlrpc) [...]:
Environnment [production]/ote (production, ote):
SSH keyfile [~/.ssh/id_rsa.pub]:
Api key (REST) [...]:

I could also be a good idea to provide xmlrpc<>REST info : xmlrpc v4 only <> REST only with v5 ?

[minusf]

i have the same issue. perhaps this tool is not compatible with gandi v5?

[grigouze]

The command compatible with v5/REST is "dns domain.list". All others are v4/xmlrpc.

[minusf]

which API key is the one coming from the admin? xmlrpc or REST?
the setup instructions show a different gandi setup than i get from the package...

[grigouze]

Can you please provide the url of the admin ? Le lun. 2 déc. 2019 à 11:48, minusf <notifications@github.com> a écrit :

…

which API key is the one coming from the admin? xmlrpc or REST? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#292?email_source=notifications&email_token=AAC3WF2DRNVHX5VYO7HGET3QWTRXVA5CNFSM4ILNQ4Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFTCFUA#issuecomment-560341712>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC3WF4C2VX66TJXBQNIODLQWTRXVANCNFSM4ILNQ4QQ> .

[minusf]

"Account security" https://account.gandi.net/en/users/my_user_name/security

[grigouze]

This one is for the REST API Le lun. 2 déc. 2019 à 12:03, minusf <notifications@github.com> a écrit :

…

"Account security" https://account.gandi.net/en/users/my_user_name/security — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#292?email_source=notifications&email_token=AAC3WF3JKVTT3SYYYKON26DQWTTQ7A5CNFSM4ILNQ4Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFTDSUI#issuecomment-560347473>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC3WF2VWGSRQ5HZ74E6X4DQWTTQ7ANCNFSM4ILNQ4QQ> .

[aegiap]

You can find your key for the XML-RPC API in our https://v4.gandi.net site in https://v4.gandi.net/admin/api_key and the key for the REST API in https://account.gandi.net/en/users/<your_login>/security

[eppfel]

This is becoming ridiculous. You are phasing out the v4 interface but still require a v4 API key. Please put some manpower behind this tool, so it does not become worthless.

[romuald]

(sorry about the noise, wrong issue)

[axelsimon]

This is becoming ridiculous. You are phasing out the v4 interface but still require a v4 API key. Please put some manpower behind this tool, so it does not become worthless.

I'm sorry to say that i agree, and to add insult to injury, following the instructions in the README creates an unusable configuration.
The Getting Started section of the README makes it look as easy as generating and copy/pasting an API key, but in reality gandi.cli (v 1.6) asks you for two different API key and the README doesn't even tell you which one it is.

Worse, trying to log in to v4.gandi.net is impossible, as it now redirects you to admin.gandi.net, making impossible to generate an XML-RPC API key at https://v4.gandi.net/admin/api_key as suggested by @aegiap.