You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Weave GitOps CLI support for Windows / document the WSL path #663
Was this closed because support is added, or has it been taken off the roadmap?
Windows support is a common question, we should leave a breadcrumb to some instructions for how to use the Weave GitOps CLI with WSL and homebrew/linuxbrew, if that's the one canonical recommended method for Windows users.
Hey @kingdonb, it's been a while since anyone commented on this issue -- what do you think we should do now/next, many months later? Still the same recommendation, or something new/different?
If there is no one to own the GitOps CLI for Windows, and one hasn't been produced yet, then I think the next best thing is to document the WSL path. I haven't been a windows user for a while, so I'm not the best person to decide the path here. But if there are any blockers to producing and testing the Windows CLI, I'd love to see them enumerated.
I think we could try cross-compiling and just put one out there, but I don't think it's entirely appropriate to take the "let any users report the bugs" approach unless we have some users we can point at who are using it with any degree of success.
Activity
kingdonb commentedon Feb 9, 2022
Was this closed because support is added, or has it been taken off the roadmap?
Windows support is a common question, we should leave a breadcrumb to some instructions for how to use the Weave GitOps CLI with WSL and homebrew/linuxbrew, if that's the one canonical recommended method for Windows users.
sympatheticmoose commentedon Mar 16, 2022
I believe this was likely closed by mistake as the team focussed on changes which have now merged. Re-opening as this is still on the radar.
lasomethingsomething commentedon Jun 16, 2023
Hey @kingdonb, it's been a while since anyone commented on this issue -- what do you think we should do now/next, many months later? Still the same recommendation, or something new/different?
kingdonb commentedon Jun 26, 2023
If there is no one to own the GitOps CLI for Windows, and one hasn't been produced yet, then I think the next best thing is to document the WSL path. I haven't been a windows user for a while, so I'm not the best person to decide the path here. But if there are any blockers to producing and testing the Windows CLI, I'd love to see them enumerated.
I think we could try cross-compiling and just put one out there, but I don't think it's entirely appropriate to take the "let any users report the bugs" approach unless we have some users we can point at who are using it with any degree of success.
@juozasg might be able to help us as a user
d3287t328 commentedon Aug 1, 2023
This would still be a nice to have. I have a connectivity issue to an environment that requires a windows vpn and WSL is broken for me.
[-]Weave GitOps CLI support for Windows[/-][+]Weave GitOps CLI support for Windows / document the WSL path[/+]DeoEsor commentedon Aug 10, 2024
+1