Current Behavior
Currently mesheryctl update downloads new versions of the Meshery containers as described in the Meshery Installation & Packaging document.
Desired Behavior
Ideally, mesheryctl update will also upgrade the binary itself (displacing itself with the latest version of the binary).
I will be working on this issue.
In the new updateCmd code I am facing a permission issue My Working Branch
behaviour
Issue faced
In case of Mac normal user "/usr/local/bin/" dir have access to write but in case of Linux normal user don't have that access to write, only root have the access for write permission.
But if we change the permission of "/usr/local/bin" to write for normal user then its working completely fine.
@NupurThakur27 have a look at gh and how it provides provides this functionality.
A new release of gh is available: 0.7.0 → v0.8.0
https://github.com/cli/cli/releases/tag/v0.8.0
@leecalcote want me to start working this?
@nitishm that'd be great, yes.
@nitishm can I work with you? I really want to learn how this is done. It seems more than just a documentation issue. More like code involved.
Is this up for grabs ? @leecalcote
Regarding having mesheryctl show latest version as message / notification to user on invoking commands. gh makes uses of github release for cli repo and manages version using github api. You can try executing GET req on https://api.github.com/repos/layer5io/meshery/releases/latest. This API results the latest release results of meshery repo. The issue with using the same approach as gh is that mesheryctl doesn't have its own repo which makes version management a bit tricky.
mesheryctl for now seems to be using the meshery version as it version tag. so things should be fine with making an implementation to check for updates similar to gh cli.
@leecalcote if the above is to be implemented. drop a message and I'll get it done right away :)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.