[
https://issues.jboss.org/browse/JBIDE-22727?page=com.atlassian.jira.plugi...
]
Dmitry Bocharov updated JBIDE-22727:
------------------------------------
Description:
The kind of Openshift resources are declated in 2 different places: WatchManager and
ConnectionWrapper. This increases the technical debt and may lead to resources displayed
by the explorer but not refreshed by the watcher.
The task requires investigation about ResourceKind.IMAGE_STREAM_TAG, which is present in
ConnectionWrapper, but there is no such element in WatchManager's array. See
discussion
[
here|https://github.com/jbosstools/jbosstools-openshift/pull/1272#discuss...]
was:The kind of Openshift resources are declated in 2 different places: WatchManager and
ConnectionWrapper. This increases the technical debt and may lead to resources displayed
by the explorer but not refreshed by the watcher.
Openshift resources managed by explorer and watcher are declared in
both place leading to inconsistency
-------------------------------------------------------------------------------------------------------
Key: JBIDE-22727
URL:
https://issues.jboss.org/browse/JBIDE-22727
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.AM1
Reporter: Jeff MAURY
Assignee: Dmitry Bocharov
Labels: explorer, openshift, openshift_v3
Fix For: 4.4.1.AM3
The kind of Openshift resources are declated in 2 different places: WatchManager and
ConnectionWrapper. This increases the technical debt and may lead to resources displayed
by the explorer but not refreshed by the watcher.
The task requires investigation about ResourceKind.IMAGE_STREAM_TAG, which is present in
ConnectionWrapper, but there is no such element in WatchManager's array. See
discussion
[
here|https://github.com/jbosstools/jbosstools-openshift/pull/1272#discuss...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)