Skip to content

Component Types View is not updated after cluster gets accessible and user logged in #2010

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dgolovin opened this issue Mar 9, 2021 · 0 comments · Fixed by #2025
Closed
Assignees
Labels
demo Show in sprint review demo kind/enhancement New feature or request priority/major
Milestone

Comments

@dgolovin
Copy link
Collaborator

dgolovin commented Mar 9, 2021

If cluster is not accessible or user is not logged in Component Types View does not show S2I components catalog. After logging in manual update is required to see S2I components available in cluster.

@dgolovin dgolovin added demo Show in sprint review demo kind/enhancement New feature or request priority/major labels Mar 9, 2021
@dgolovin dgolovin added this to the v0.2.4 milestone Mar 9, 2021
@dgolovin dgolovin self-assigned this Mar 10, 2021
@dgolovin dgolovin changed the title Component Types View is not updated after cluster gets acessible or user logged in Component Types View is not updated after cluster gets acessible and user logged in Mar 11, 2021
dgolovin added a commit to dgolovin/vscode-openshift-tools that referenced this issue Mar 11, 2021
dgolovin added a commit that referenced this issue Mar 11, 2021
…2025)

* Refresh Component Types View right after Application Explorer View

This PR fixes #2010.

Signed-off-by: Denis Golovin [email protected]
@dgolovin dgolovin changed the title Component Types View is not updated after cluster gets acessible and user logged in Component Types View is not updated after cluster gets accessible and user logged in Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
demo Show in sprint review demo kind/enhancement New feature or request priority/major
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant