Deprecate tool if abandonned about gandi.cli HOT 5 CLOSED

I'm sorry to revisit this issue, but the tool is currently unusable: it actually requires two API keys, which the README doesn't even warn you about properly, and one of these two keys can only be obtained from https://v4.gandi.net/admin/api_key which no longer exists (issue #303).

It is therefore impossible to generate a working config for new users, making the tool useless.

Please consider adding a warning on the README warning users about this situation and/or deprecating the tool if no work is being done to maintain it

from gandi.cli.

I've come to expect better from gandi than this. I wasted more than an hour of my time and had to come to the conclusion that gandi.cli is basicly abandonware . Gandi, please either label it as such or invest in it.

from gandi.cli.

Gandi could at least give us information about this issue.

As a paying customer who has a lot of domains, it really begins to be a pain in the *** to not be able to use the cli anymore.

I already migrated all my cloud instances to another provider as I found they were overpriced compared to others for the same level of performance and customer service.

I will soon do the same for my domains to finally be able to automate records management again

from gandi.cli.

Right, just saw that one hour ago (!) a 1.6 version was released. So the project is still active :)

from gandi.cli.

This repo has been marked as deprecated in #313.

If gandi.cli worked for you it will continue to do so, otherwise we won't be able to maintain it; the hybrid approach between v3/v4 and v5 is not really maintainable, sorry.

As mentioned in #313, for now you can use the JSON REST APIs at https://api.gandi.net/docs/ (curl | jq is a good start); and the openstack cli for GandiCloud VPS.

from gandi.cli.