CLI makes incorrect (!?) references to NAME when ID is expected

Example:

podman run \
--interactive --tty \
--volume=${HOME}/.koyeb.yaml:/.koyeb.yaml \
docker.io/koyeb/koyeb-cli:${VERS} \
services list
ID      	APP    	NAME    STATUS 	CREATED AT          
12345678	{app}	{name}	HEALTHY	21 Jun 23 16:30 UTC
services get --help
Get service

Usage:
  koyeb services get NAME [flags]
services get {name}
FATA[0001] id not found "{name}"      
services get 12345678
ID      	APP    	NAME    STATUS 	CREATED AT          
12345678	{app}	{name}	HEALTHY	21 Jun 23 16:30 UTC	

From recollection, this occurs consistently incorrectly across the CLI (get apps, get deployments etc.)

Also, the ID as presented by the CLI is a short-form. The underlying e.g. service_id is a UUID. This confused me as I began using the Koyeb API where CLI ID values (as presented) don’t work.

Hi @Daz_Wilkin,

Thank you for reporting it. We are currently working on the CLI to improve it. Currently, it’s working, but the experience using it is far from ideal.

apps get accepts NAME while services get and deployment get require ID.

1 Like

Thanks Sebastian!

Yes, I realized after posting (and forgot to update the post) that, apps does use NAME

The CLI is good.

Making a good CLI is hard.

It’s consistent, comprehensive, supports --output={structured} which is very helpful.

1 Like

You have to prefix the service name with the application name: koyeb services get <app_name>/<service_name>

1 Like