Should "odo list" not fail when not logged into the OpenShift cluster?

[dharmit]

User Story

As a user or (ide plugin) I would like to list all components in a given path and I should not be required to be connected to the cluster.

Current behaviour

# not logged into OpenShift (CRC) yet
$ odo list --path ~/src
APP     NAME         TYPE       SOURCE                      STATE          CONTEXT
app     backend      java       target/wildwest-1.0.jar     Not Pushed     /home/dshah/src/Wild-West-Backend
app     frontend     nodejs     ./                          Not Pushed     /home/dshah/src/Wild-West-Frontend
app     node         nodejs     ./                          Not Pushed     /home/dshah/src/nodejs-ex

# let's login
$ odo login -u developer
Connecting to the OpenShift cluster

Authentication required for https://api.crc.testing:6443 (openshift)
Username: developer
Password: 
Login successful.

You have one project on this server: "myproject"

Using project "myproject".

# now it shows the components' STATE as Pushed!
$ odo list --path ~/src
APP     NAME         TYPE       SOURCE                      STATE          CONTEXT
app     backend      java       target/wildwest-1.0.jar     Pushed         /home/dshah/src/Wild-West-Backend
app     frontend     nodejs     ./                          Pushed         /home/dshah/src/Wild-West-Frontend
app     node         nodejs     ./                          Not Pushed     /home/dshah/src/nodejs-ex

Acceptance Criteria

• odo list --path should work without odo being logged or connected to the cluster
• if odo list --path command can't determine the correct state (Pushed, Not Pushed), because it is not connected to the cluster, the component should have an Unknown state.
  Example:

  $ odo list --path ~/src
  APP     NAME         TYPE       SOURCE                      STATE          CONTEXT
  app     backend      java       target/wildwest-1.0.jar     Unknown     /home/dshah/src/Wild-West-Backend
  app     frontend     nodejs     ./                          Unknown     /home/dshah/src/Wild-West-Frontend
  app     node         nodejs     ./                          Unknown     /home/dshah/src/nodejs-ex
  

[kadel]

Should it not fail? This gives a false indicator that the components are not pushed and user might try to do odo push instead.

The command should NOT fail. odo list --path ~/src intention is to find components, and cluster connection shouldn't be required.
But the current behavior is also not correct and can be misleading.

If we can't verify the state of the component for some reason, we should show unknown state.

$ odo list --path ~/src
APP     NAME         TYPE       SOURCE                      STATE          CONTEXT
app     backend      java       target/wildwest-1.0.jar     Unknown     /home/dshah/src/Wild-West-Backend
app     frontend     nodejs     ./                          Unknown     /home/dshah/src/Wild-West-Frontend
app     node         nodejs     ./                          Unknown     /home/dshah/src/nodejs-ex

/priority medium

[girishramnani]

This issue seems well defined in terms of what work needs to be done. So no further analysis needed in my opinion.

[kadel]

/triage ready

[adisky]

/assign