Hide `odo` terminal by default and bring it up in case of error output

[kadel]

As an extension user, I don't care about odo dev output. It is distracting me from code.
The terminal should be hidden and its output should be in the OpenShift extension "OUTPUT" tab like it is with other extensions

[dgolovin]

@kadel I would suggest still use Terminal, but just not bring it up. Would that work? The main reason is using OpenShift Extension output for everything is not good for parallel tasks, because it is not going to be readable. Using one Output channel per 'odo dev' running would pollute VSCode Ouptput channels view.

[mohitsuman]

Having everything in One Output channel is not intuitive. I would not recommend it. Having odo dev output in the terminal allows users to easily see how the K8s resources are created and the progress of the command.

For errors in the command, the terminal view atleast differentiates in vscode panel (on the right side of terminal).

[kadel]

If it doesn't pop-up automatically terminal would work as well.

Having odo dev output in the terminal allows users to easily see how the K8s resources are created and the progress of the command.

The whole point of the IDE plugin is that it provides native interface for IDE users and hides odo cli. The goal should be that the progress and everything else is shown using the IDE elements.

 For errors in the command, the terminal view at least differentiates in vscode panel (on the right side of the terminal).

If the extension detects that there is an error in odo's output, there should be a VSCode notification (or whatever it is called that is shown on the bottom right corner), or just show the terminal once the error is detected with the output would work as well.

The thing is that this whole experience where the terminal automatically pops up, is distracting and it creates a feeling that the extension is just a "dump" wrapper that only executes commands in the terminal. Which definitely is not true.

[dgolovin]

@kadel

Do not show terminal by default is a good first step I can do easily.

Bringing terminal up on error output is also easy fix

Hiding odo cli completely is totally depends on odo json output sending all state related info to IDE in reliable and consistent way through all odo releases. There should be specific events for component running with odo and react on or pass them to the user. Like:

• debug port forwarded
• frontend port forwarded
• Input request from user
• Message to show to user
• and etc

[kadel]

Hiding odo cli completely is totally depends on odo json output sending all state related info to IDE in reliable and consistent way through all odo releases. There should be specific events for component running with odo and react on or pass them to the user. Like:

• debug port forwarded
• frontend port forwarded
• Input request from user
• Message to show to user
• and etc

we can do that, just open an issue on the odo repo describing what information and in what format you require.