feat: Windows Chocolatey package

[wilsonwaters]

closes #79

Windows users can choco install algokit and get the latest production version of algokit installed to their machine

TODO

• Create package .nuspec file
• Create python 3.10 as a dependency
• write chocolateyinstall.ps1 to install algokit from bundled wheel file using pipx
• write chocolateyuninstall.ps1 to remove algokit using pipx
• Github actions to upload new package on manual release
• Github actions to upload new prelease package continuous deployment (automatic based on version slash notation x.y.x-beta)
• bundle pre-built wheel file as part of github actions
• determine wheel file version and pass to choco pack
• set .nuspec Project URL and documentation URLs (when known) (used https://github.com/algorandfoundation/algokit-cli) for now
• set icon (png, transparent, 128x or higher) and host it somewhere (used https://www.algorand.com/assets/media-kit/logos/logo-marks/png/algorand_logo_mark_black.png for now)
• Create https://community.chocolatey.org/ API key used to publish package (Alessandro? Add key to Github secrets) (requested from Shane McGovern)
• Confirm choco upgrade algokit to upgrade to latest available version
• Confirm choco uninstall algokit to remove algokit cli from a system
• Add comments to install docs indicting that using chocolatey will install a new python and add it to start of your path (potentially clobbering any pre-installed python version). If you already have python installed, suggest to use the pipx method. Alternatively, run choco install --ignoredependencies algokit to use existing python (use at own risk)
• remove dependency on crazy-max/ghaction-chocolatey. Call chocolatey directly in a windows again (it should even be pre-installed!)

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
src/algokit
__init__.py	15	7	53%	6–13, 17–24, 32–34
__main__.py	2	2	0%	1–3
src/algokit/cli
completions.py	103	1	99%	91
init.py	165	16	90%	57, 204–205, 236, 239–241, 252, 290, 327, 336–338, 341–346, 361
sandbox.py	84	1	99%	155
src/algokit/core
bootstrap.py	133	16	88%	109, 129, 201, 204, 210–224
click_extensions.py	47	20	57%	40–43, 50, 56, 67–68, 73–74, 79–80, 91, 104–114
conf.py	30	4	87%	13, 17, 25, 27
doctor.py	54	3	94%	63–65
log_handlers.py	68	9	87%	44–45, 50–51, 63, 112–116, 125
proc.py	44	1	98%	95
sandbox.py	112	7	94%	86, 151, 167, 182–184, 199
version_prompt.py	70	9	87%	27–28, 33, 52–55, 66, 76, 105
TOTAL	1114	96	91%

Tests	Skipped	Failures	Errors	Time
156	0 💤	0 ❌	0 🔥	9.393s ⏱️

[wilsonwaters]

Building locally

• ensure wheel file is built poetry build (make sure there's only a single file in dist)
• update version in algokit.nuspec
• cd .\scripts\chocolatey\algokit
• choco pack
• choco apikey --api-key [API_KEY_HERE] -source https://push.chocolatey.org/
• choco push --source https://push.chocolatey.org/

Installing/testing locally

• choco install algokit -pre --source "'.;https://community.chocolatey.org/api/v2/'" -y
• choco uninstall algokit -y
• choco upgrade algokit -pre --source "'.;https://community.chocolatey.org/api/v2/'" -y

[wilsonwaters]

Should we switch to the fixed version of copier while we're waiting for copier-org/copier#890 ?

[robdmoore]

yep

[robdmoore]

This is interesting. It means that if you already have python installed globally then god knows what this will do (worth testing?).

[wilsonwaters]

You're right. Python version hell.

For me, it installed a new version and added it at the beginning of my path.

Everything still worked, but yea, that might annoy people who already have a specific version of python installed.

[wilsonwaters]

I think for some chocolatey packages it will try to determine if it's already been installed manually and "take over". But doesn't seem to do this for python (fortunately?)

[achidlow]

Can we depend on >=3.10.0 here instead?

[robdmoore]

Can we assume python will work?

[wilsonwaters]

If python has been installed successfully as a dependency, then I can't see why not? Do you think I should do a test and print a useful error message (rather than a slightly obscure "command not found" error).

[achidlow]

I understand the logic here, but this makes our package not idempotent due to also requiring pipe for uninstall. Can we make pipx a dependency instead? This would mirror our home-brew package, and pipx is actually an (optional) runtime dependency (for installing poetry if not already installed during bootstrap)

[robdmoore]

There's no pipx package for chocolatey.

[wilsonwaters]

Shamelessly stolen from @daniel-makerx here

[wilsonwaters]

I gathered having a separate job (and yaml file) for packages makes sense? We could potentially publish all our packages from the publish-release-packages.yaml files (i.e. brew and chocolatey. And potentially pypi). Keeps all package publishing together and allows us to trigger them all based on a single condition.

Otherwise I'm happy to move the whole publish-release-packages.yaml here into cd.yaml

[wilsonwaters]

Seems the Chocolaty community repo automated tests failed due to the copier package not installing. The image they use to test installing the packages does not have git, so it couldn't use our hacky fix in pyproject.toml pointing to my github fork of copier.

We'll need to wait until copier release an alpha package to pypi...

2022-12-20 18:01:46,878 5092 [INFO ] - pip seemed to fail to build package:
2022-12-20 18:01:46,894 5092 [INFO ] -     copier@
2022-12-20 18:01:46,894 5092 [INFO ] - System.Management.Automation.RemoteException
2022-12-20 18:01:46,910 5092 [INFO ] - Some possibly relevant errors from pip install:
2022-12-20 18:01:46,910 5092 [INFO ] -     ERROR: Error [WinError 2] The system cannot find the file specified while executing command git version
2022-12-20 18:01:46,925 5092 [INFO ] -     ERROR: Cannot find command 'git' - do you have 'git' installed and in your PATH?

https://gist.github.com/choco-bot/f7f5353bab35c18811de2a2843516c18