-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
internal/olm: get installed version from cluster instead of required CLI argument #1634
internal/olm: get installed version from cluster instead of required CLI argument #1634
Conversation
@estroz Makes sense to me to use it for uninstall. |
…) in Manager.Status()
--version is only used with Install. internal/olm/manager.go: use Client.GetInstalledVersion() in Manager.Uninstall() instead of requiring version.
5affa6a
to
4fdf055
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
After addressing comments and if OLM agrees that this is a reasonable way to determine the OLM version.
@joelanford indeed they do: operator-framework/operator-lifecycle-manager#935. |
4fdf055
to
3db2094
Compare
New changes are detected. LGTM label has been removed. |
Co-Authored-By: Joe Lanford <joe.lanford@gmail.com>
/test e2e-aws-ansible |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One nit. Otherwise LGTM
@estroz Can you also update |
Description of the change: get the version of OLM installed in a cluster without passing
--version=<version>
toolm status
.Motivation for the change: a user may not know which OLM version was installed in a cluster.
@joelanford we might be able to use
Client.GetInstalledVersion()
inUninstall()
too.