Make windows airy create work

[chrismatix]

Current state

We build and provide CLI binaries for Windows, but have sofar not tested them or invested any development effort into making them work.

(thanks to @Decmcc for the screenshot)

Desired state

We don't want to officially support windows for a lack of capacity and developer share.

As an airy user
Given that I have downloaded the windows CLI binary
When I run the create --provider minikube command
Then I have a working minikube installation with support for cli commands

TODO:

• Implement user story
• Update docs to say that windows is supported unofficially

[ljupcovangelski]

The problem with airy create on Windows is because the path of embedded file is read wrong. This line causes problem
https://github.com/airyhq/airy/blob/develop/cli/pkg/workspace/template/copy.go#L43

Even though bazel builds it correctly for Windows with "" instead of what is the default for *nix "/".

I tested with

content, err := templateDir.ReadFile("src/airy.yaml")

and it works correctly.

Also in the embed package, they have stated that: The path separator is a forward slash, even on Windows systems.

[chrismatix]

@ljupcovangelski That's very interesting. It means that we are reading the embedded directory wrong, because we use filepath.join which seems to use OS-specific path delimiters.

So to fix this we need to recursively list the template directory without relying on that method.

[ljupcovangelski]

The embedded path was fixed and now airy create starts the provisioning on Windows. However, I was still getting some issues when the helm chart is deployed, that the images cannot be pulled

Failed to pullimage "busybox": rpc error: code = Unknown desc = Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.0.2.3:53 read udp i/o timeout

It needs some more testing and debugging.