From: Giovanni Biscuolo <g@xelera.eu>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix mailing list <help-guix@gnu.org>
Subject: Re: Useless gandi.cli (was: [bug#39447] [PATCH] gnu: Add python-gandi.cli.)
Date: Wed, 18 Mar 2020 16:36:43 +0100 [thread overview]
Message-ID: <874kulisj8.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <87d09bl0k5.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]
Tobias Geerinckx-Rice <me@tobias.gr> writes:
[...]
>> https://v4.gandi.net/admin/api_key
>
> I'd love to, but that doesn't work for everyone anymore:
>
> Account already migrated
> This account has already been migrated to Gandi's new
> website. […]
Mumble... actually I don't know why but I'm able to log in in V4 (using
the "legacy" handle") and V5
> That message is new. When I opened this bug a week ago, logging
> into V4 still broke IceCat with a redirect loop, with no
> indication of what went wrong. I haven't changed or updated my
> browser since.
The joy of web interfaces :-S
>> They are planning to close the v4 customer web interface, I hope
>> they
>> will fix this before... but fortunately it's still working
>
> I'm glad to hear it's still working for you
ehrm, ehrm: actually I never used gandi.cli and I'm testing it in my
spare time
1. the legacy "gandi domain list" just lists the domanins of my "legacy"
v4 handle
2. "gandi dns domain.list" (the v5 equivalent) gives an empty list
3. curl -H "Authorization: Apikey $GANDI_APIKEY" https://api.gandi.net/v5/domain/domains
gives me the complete list (that means the domains in all the organizations I'm part of)
> at least, and I suspect someone who really needs the CLI could ask
> support for an XMLRPC key. That's enough to keep it in Guix. It was
> not enough to keep me with Gandi.
gandi.cli needs more love:
1. https://github.com/Gandi/gandi.cli/issues/279
Unable to manage domains migrated to Gandi-V5
2. https://github.com/Gandi/gandi.cli/issues/288 (Order domain name via API V5)
and probably also the API:
1. https://github.com/Gandi/gandi.cli/issues/285
dns update command reports "Remote API service is unreachable"
that bugs are still open, they made some commits since the 1.5 release
but AFAIU by a quick look at the code that ploblems are still open (and
probably upgrading gandi.cli to a newer commit won't enhance the
situation)
[...]
Ciao, Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2020-03-18 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200206031305.20513-1-mab@gnu.org>
2020-03-11 3:54 ` Useless gandi.cli (was: [bug#39447] [PATCH] gnu: Add python-gandi.cli.) Tobias Geerinckx-Rice
2020-03-17 8:06 ` Giovanni Biscuolo
2020-03-17 10:52 ` Tobias Geerinckx-Rice
2020-03-18 15:36 ` Giovanni Biscuolo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kulisj8.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).