channel: stable
version: v0.4.27
with version being optional and -latest being implied if version isn't supplied in that, afterall, users will have subscribed to a release channel.
Allow users to deal (start, stop, reset, log) with multiple platforms. Few examples
Docker: use docker-compose (using extend)
Kubernetes - use kubernetes client go
Podman - podman-compose
The meshery.yaml is modified and maintained by viper. The selected context configuration is reflected in the meshery.yaml by viper.
Allow deployment of specific version of meshery as well as subscription to channels
Stable
Edge
Specific Version to use version tags: stable-{$version}
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.
@metonymic-smokey will you verify that what is describe here is the current behavior of this command?
@leecalcote , I'll get to this!
Give me a week to test it out.
@kumarabd
When I run the mesheryctl system channel command in the issue, I get an error stating --version is not a valid flag.

From what I understood, this issue is about verifying the behaviour of mesheryctl system channel commands but --version and --channel flags are not yet added to mesheryctl?
When i remove version from config.yaml or change channel in the file to latest, those work as expected, when I run mesheryctl system channel view.
Thanks!
@leecalcote does this issue also involve adding support for the two flags mentioned in the issue or is it just verifying and documenting the available flags and their behaviour?
Thanks!
@metonymic-smokey, if you think you have a handle on adding the two flags, let's proceed with both adding them and documenting the command. 馃憤
@leecalcote @metonymic-smokey --context flag is global to all the system commands in mesheryctl. Add the --context flag will switch the context temporarily. This is implemented in the system channel command.
To specify the channel and version, we could use something like mesheryctl system channel set stable-v0.5 as per the current implementation by @anirudhjain75
The problem with adding a --version -v flag is the we have a --verbose -v flag globally for all mesheryctl commands.
So, I think it is fine to keep the current implementation as it is. (I hope I'm not missing anything else)
@navendu-pottekkat got it!
I thought it would be neater to have a separate --version flag with another shorthand but i think you have a point saying the current implementation is fine.
I'll just check the docs for these flags and work on them then.
Thanks!
Yes, I agree that it would be neat. But if that collides with the --verbose flag, it would be better if we keep it this way.(Although we do not have much verbose logs in mesheryctl)
@leecalcote @kumarabd , we have this functionality already added in the context set [release-version] command. Closing this issue...