Closed jsturtevant closed 3 years ago
@fishnix would you be able to help?
Hi @jsturtevant, thanks for the PR! I'll find some cycles to review.
Thanks for finding the time to review! I addressed the comments. If I pushed a github action for building and running the tests on PR would you be interested?
output from a build:
==> vhd-windows-2019: Provisioning with Goss
==> vhd-windows-2019: Configured to run on Windows
//truncated
vhd-windows-2019: "summary": {
vhd-windows-2019: "failed-count": 0,
vhd-windows-2019: "summary-line": "Count: 3, Failed: 0, Duration: 2.648s",
vhd-windows-2019: "test-count": 3,
vhd-windows-2019: "total-duration": 2648382900
vhd-windows-2019: }
vhd-windows-2019: }
==> vhd-windows-2019: Goss validate ran successfully
@fishnix Thanks for the initial review. I addressed most comments would you take a look again? Thanks!
@jsturtevant thanks for the fixes! 🙇 I'm sorry I haven't had a chance to review this. I will as soon as I can. Cheers!
This provisioner is used to provide goss testing in the image-builder project. I recently added Windows support to image-builder and would like to run the goss test against it during provision in the same manner as the other images. Goss also now has alpha support for Windows.
I've updated the code here to support Windows and added a few tests.
Here is the output of it running against a windows VM. It is using a custom goss url while I wait for the fix in goss https://github.com/aelsabbahy/goss/pull/666