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

Offer only allowed updates on UI/CLI #344

Open
Tracked by #112
christophenne opened this issue Mar 8, 2024 · 2 comments
Open
Tracked by #112

Offer only allowed updates on UI/CLI #344

christophenne opened this issue Mar 8, 2024 · 2 comments
Milestone

Comments

@christophenne
Copy link
Member

christophenne commented Mar 8, 2024

Is your feature request related to a problem? Please describe.
As of now, we show the update button (and the "vX.Y.Z available" in the CLI) whenever the latestVersion is not the installed version. The first problem with this is, that the user might be on a more current version than latest (see #329). The second one is, that it might not be possible to update to the latest version, because the package is required as a dependency by another package, or because a dependent package cannot be updated. Maybe there are even more cases where an update is not possible – TBD.

Describe the solution you'd like
UI/CLI should only offer the user to only show the updates that are possible in their cluster. This means that a package might not be able to be updated to latest version but to a version below that, or maybe not be able to be updated at all.

Parts of this have been done in #401 – but right now we don't offer the latest possible version to update to, we just don't offer an update at all.

Describe alternatives you've considered
Not implementing this and instead showing an error to the user that the update is not possible. This would still be possible but be a bit confusing and inconsistent. Also, it would not be possible to update to a lower version than latest.

Additional context
Kind of related in terms of same code that will be touched: #329
Prior work on this: #401

@hanshal101
Copy link
Contributor

Hey @christophenne I would like to work on this. Can you give me some more information on this.

@christophenne
Copy link
Member Author

Hi @hanshal101, thanks a lot, but we have to talk about this one internally first, I think it's better to pick another issue – as always the ones labelled "help wanted" are a good choice. If you are still interested in #441 for example, and if you don't have any other issues assigned right now (except for the one where the PR is open), I think that would be a good issue to look at now.

@pmig pmig modified the milestones: v0.3.x, v0.4.x Apr 29, 2024
@pmig pmig modified the milestones: v0.4.x, v0.5.0 May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants