Skip to content
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

Inconsistent module status presentation across busola #3458

Open
arturskorupa opened this issue Nov 7, 2024 · 1 comment
Open

Inconsistent module status presentation across busola #3458

arturskorupa opened this issue Nov 7, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@arturskorupa
Copy link

Description

Busola presents module status on 2 views - one is rendered after one click edit modules on an overview page - there the status of modules is correct. Another is accessible from the path "kyma-system namespace view -> Kyma resource -> default" and there the status is wrong (it's taken from Kyma CR instead of module manifests)

Expected result

Status should be presented consistenlty across the application and it should be like on edit module view (accessible from the cluster overview page)

@mrCherry97 mrCherry97 added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 8, 2024
@mrCherry97
Copy link
Contributor

hi @arturskorupa
this view is generated via Extensibility, and its Installation state is taken from Kyma CR (because you are on the Kyma resource view). To display the modules' status, we need to dynamically fetch all the installed modules, which is impossible right now. We will take a look if it's possible to add a custom function to fetch dynamically this data from all of the modules, if it is problematic, then we will change the name of the column to Installation State as it is on the Modules view.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants