The VagrantCloud Hyper-V box version 2020.04.15 isn't being discovered by Vagrant

[yeroc-sebrof]

Hey was looking for a Hyper-V Windows Server and found yours but it seems to have skipped the most recent version in favour of 2020.02.12

PS C:\VirtualMachines> vagrant up
Bringing machine 'default' up with 'hyperv' provider...
==> default: Verifying Hyper-V is enabled...
==> default: Verifying Hyper-V is accessible...
==> default: Box 'StefanScherer/windows_2019' could not be found. Attempting to find and install...
    default: Box Provider: hyperv
    default: Box Version: 2020.04.15
==> default: Loading metadata for box 'StefanScherer/windows_2019'
    default: URL: https://vagrantcloud.com/StefanScherer/windows_2019
The box you're attempting to add has no available version that
matches the constraints you requested. Please double-check your
settings. Also verify that if you specified version constraints,
that the provider you wish to use is available for these constraints.

Box: StefanScherer/windows_2019
Address: https://vagrantcloud.com/StefanScherer/windows_2019
Constraints: 2020.04.15
Available versions: 2018.10.03, 2018.11.22, 2019.01.18, 2019.02.14, 2019.03.13, 2019.04.11, 2019.05.15, 2019.05.22, 2019.09.12, 2019.09.26, 2019.10.09, 2019.11.15, 2020.01.15, 2020.02.12, 2020.02.26, 2020.07.17, 2020.09.22

[StefanScherer]

Hey @yeroc-sebrof that's correct. The CI pipeline to build the hyperv boxes is broken for a long time and I hadn't time to look at it and also nobody who seems to use the Hyper-V boxes.
You're the first one that gives feedback that it seems there is demand for it ;-)
Maybe I find some time to look into what got broken and I can kick off a build for the next Windows update cycle.

[sqeezy]

Me personally and my company are using the Hyper-V boxes from this repository on a regular basis. Due to the nature of our use case, we don't update every version as soon as it is released but when we get to it. If there is a way of helping you to fix the CI-Issues, let me know and I will have a look myself.
In any case I want to express my gratitude for your work on this project specifically and also your work in the more general virtualization/containerization space. Always a good resource and source of inspiration.

[StefanScherer]

Thank you @sqeezy 😊
Well I didn't look deeper what was wrong, but I hadn't the time to fix it at that point. One of the failing jobs was https://app.circleci.com/pipelines/github/StefanScherer/packer-builder/61/workflows/bf097759-da8c-4cb8-9357-eb1e441af5ad/jobs/1304 - ok that looks like outdated secrets or something like that. Well it often depends on the tools used to create the build agent. A breaking terraform update, sometimes a new packer version, ... The remote ssh connection is a bit tricky, but that gave me the coloured output in the CircleCI builds.
The repo to run the builds is https://github.com/StefanScherer/packer-builder, CircleCI runs machine.sh which uses terraform to spin up an Azure V3 box and installs packer on it to run the actual build.
At least showing interest in this issue shows me that it would make sense to build Hyper-V boxes again. I don't have download metrics on app.vagrantup.com per hypervisor, only one total downloads per version.