vscode-openshift-tools
vscode-openshift-tools copied to clipboard
Distinguish healthy and unhealthy pushed components in Application Explorer
When component pushed and build failed component still reported as pushed because deployment config is present and odo reports it that way. In this state some of the commands (open in browser, follow log, debug) are useless because component is not running. Component state should extended to pushed healthy or pushed unhealthy, so tools can provide commands relevant for specific state.
Example is deploying quarkus project using java-maven devfile (see comment for details https://github.com/redhat-developer/vscode-openshift-tools/issues/1800#issuecomment-712688321)