✨ Add commands to list and get olmv1 operators and catalogs

[azych]

This adds get command that enables getting/listing olmv1 operators(ClusterExtensions) and catalogs (ClusterCatalogs) via the CLI.

Syntax follows the get behavior of kubectl:
olmv1 get operator(s) - list all operators
olmv1 get operator(s) <name> - get details of a single operator
olmv1 get catalog(s) - list all catalogs
olmv1 get catalog(s) <name> - get details of a single catalog

Commands return data in the following format similar to kubectl output, with catalogs being sorted by availability, priority and name; operators being sorted by name:

➜  go run *.go olmv1 get operator
NAME       INSTALLED BUNDLE            VERSION  SOURCE TYPE  INSTALLED  PROGRESSING  AGE
argocd     argocd-operator.v0.6.0      0.6.0    Catalog      True       True         5h44m
zookeeper  zookeeper-operator.v0.17.8  0.17.8   Catalog      True       True         24s
➜  go run *.go olmv1 get operators
NAME       INSTALLED BUNDLE            VERSION  SOURCE TYPE  INSTALLED  PROGRESSING  AGE
argocd     argocd-operator.v0.6.0      0.6.0    Catalog      True       True         5h44m
zookeeper  zookeeper-operator.v0.17.8  0.17.8   Catalog      True       True         30s
➜  go run *.go olmv1 get operator zookeeper
NAME       INSTALLED BUNDLE            VERSION  SOURCE TYPE  INSTALLED  PROGRESSING  AGE
zookeeper  zookeeper-operator.v0.17.8  0.17.8   Catalog      True       True         37s
➜  go run *.go olmv1 get operators zookeeper
NAME       INSTALLED BUNDLE            VERSION  SOURCE TYPE  INSTALLED  PROGRESSING  AGE
zookeeper  zookeeper-operator.v0.17.8  0.17.8   Catalog      True       True         41s
➜  go run *.go olmv1 get catalog
NAME              AVAILABILITY  PRIORITY  LASTUNPACKED  SERVING  AGE
notoperatorhubio  Available     0         13s           True     20s
operatorhubio     Available     0         103m          True     5h46m
➜  go run *.go olmv1 get catalogs
NAME              AVAILABILITY  PRIORITY  LASTUNPACKED  SERVING  AGE
notoperatorhubio  Available     0         19s           True     26s
operatorhubio     Available     0         103m          True     5h46m
➜  go run *.go olmv1 get catalog operatorhubio
NAME           AVAILABILITY  PRIORITY  LASTUNPACKED  SERVING  AGE
operatorhubio  Available     0         103m          True     5h47m
➜  go run *.go olmv1 get catalogs operatorhubio
NAME           AVAILABILITY  PRIORITY  LASTUNPACKED  SERVING  AGE
operatorhubio  Available     0         103m          True     5h47m

closes operator-framework/operator-controller#1767

cc @ankitathomas

[joelanford]

get and list should not be separate subcommands. With kubectl, one can list by simply leaving the name argument out of the command args.

So

• kubectl operator get catalog(s) -> lists the ClusterCatalogs
• kubectl operator get catalog(s) my-catalog -> gets the ClusterCatalog called my-catalog`

[azych]

get and list should not be separate subcommands. With kubectl, one can list by simply leaving the name argument out of the command args.

So

* `kubectl operator get catalog(s)` -> lists the ClusterCatalogs

* `kubectl operator get catalog(s) my-catalog -> gets the ClusterCatalog called `my-catalog`

I was going by the separation that already exists in olmv0 commands but this approach would be my preference as well, so happy to make the changes

[perdasilva]

I don't think it's necessary to get this PR down. But, if it's easy enough, it would be cool to have an asciinema demo attached to the PR description (maybe even the script checked-in with the PR =D)

[azych]

I don't think it's necessary to get this PR down. But, if it's easy enough, it would be cool to have an asciinema demo attached to the PR description (maybe even the script checked-in with the PR =D)

good idea, though I'd suggest doing that once we have all the other new olmv1 commands that we're looking to add already in place, so we can have a single, self-contained demo just working with new CLI commands and showing e2e functionality. I'd imagine this demo would end up in README the same like it is now for olmv0.

I'll create an issue for this to keep track: operator-framework/operator-controller#1807

[perdasilva]

Some small nits around comments and wondering whether we ought to also test the sort order. But, not super worried about it. Leave it to you to decide ^^ otherwise - looks nice! very concise and easy to read. Thank you!

[grokspawn]

Great job @azych!