kn service get <service-name> will list all the services

[savitaashture]

Get all the services in particular namespace

kn service get -n test
NAME           DOMAIN                          GENERATION   AGE    CONDITIONS   READY     REASON
autoscale-go   autoscale-go.test.example.com   1            124m   0 OK / 3     Unknown   RevisionMissing : Configuration "autoscale-go" is waiting for a Revision to become ready.
test1          test1.test.example.com          1            118m   0 OK / 3     False     RevisionMissing : Configuration "test1" does not have any ready Revision.

get a particular service by specifying service name

current:

kn service get -n test autoscale-go
NAME           DOMAIN                          GENERATION   AGE    CONDITIONS   READY     REASON
autoscale-go   autoscale-go.test.example.com   1            125m   0 OK / 3     Unknown   RevisionMissing : Configuration "autoscale-go" is waiting for a Revision to become ready.
test1          test1.test.example.com          1            119m   0 OK / 3     False     RevisionMissing : Configuration "test1" does not have any ready Revision.

Expected: Should list only that perticular service.
something like below

kn service get -n test autoscale-go
NAME           DOMAIN                          GENERATION   AGE    CONDITIONS   READY     REASON
autoscale-go   autoscale-go.test.example.com   1            125m   0 OK / 3     Unknown   RevisionMissing : Configuration "autoscale-go" is waiting for a Revision to become ready.

Because of above behavior when we do

kn service get -n test autoscale-go -o yaml

It will give the detailed yaml info for all the services.

Applicable for all kn commands

[navidshaikh]

Resource name as argument to get command is not implemented, get command's behavior is to list all resources in requested namespace. Single resource's get is actually describe command in human readable format which should support different output formats with -o option. @rhuss is on it check #75

[rhuss]

@navidshaikh I think get should be able to list a single resource as well (in short form), much like kubectl get does, too. This is especially useful for machine-readable output (-o json). We could use the name as literal or as a prefix file (which would be nice for revisions to catch all similar revisions).

kn service describe then is for detailed human-readable output only, but kn get service myservice -o yaml is important so that kn can easily be used for scripting, too.

[navidshaikh]

@rhuss : sounds good, +1

kn get service myservice -o yaml is important so that kn can easily be used for scripting, too.

👍

[savitaashture]

@rhuss @navidshaikh Thank you

/assign

[rhuss]

Fixed with #150