Publish Scoop manifest

[paultyng]

This exists in Goreleaser, see #47

Terraform has one as an example: https://github.com/ScoopInstaller/Main/tree/master/bucket

Not sure if this can be fully automated, never really used Scoop myself, you will need to PR an initial manifest, but it looks like it can do some version handling automation once you do.

[radeksimko]

As for automation - the idea is that we'd create our own bucket (e.g. github.com/hashicorp/scoop-bucket, or something LS specific) and GoReleaser can update that automatically.

See GoReleaser's own bucket: https://github.com/goreleaser/scoop-bucket

[adamency]

can we have an update on this ?

[radeksimko]

@adamency We don't have this on the near-term roadmap, but it would help us prioritize it if you were to share some details about your situation.

FWIW The VS Code extension https://github.com/hashicorp/vscode-terraform currently embeds the LS such that out-of-bound installation is not necessary. For various reasons we have very little data available about the usage of other clients that could be fed into our decision making about priorities, so we rely primarily on GitHub data like comments and upvotes here.

What client/editor do you use?

[adamency]

Thanks a lot for your prompt response ! I use Neovim and on Windows :). Which is why I currently have to retrieve the latest binary here every time there's an update. And I dare believe that a lot of other devops/sysops engineers use Vim/Neovim too ;). Having a scoop package would simplify updating the program and also be a godsend for automating configuration of systems !

I feel like scoop is really the right choice on Windows-side, as opposed to winget and choco considering the scope of the project, all the more given that goreleaser has the already done the wiring for us.

I would be glad to help by making an initial PR for this, unfortunately I don't have any experience in building a Scoop package and don't have the time to dive into it right now. Maybe later...