Extension renaming does not work correctly on Windows

[roborourke]

When running vagrant up or provisioning for the first time the expected file paths for extensions on Windows are reported incorrectly, this results in an error stating that Puppet was unable to create symlinks for extension manifest files eg:

ln: creating symbolic link `/vagrant/puppet/manifests/chassis_redis.pp': Protocol error

I'm not 100% sure why this happens but it could be due to the extension renaming code attempting to lowercase directory paths even on case insensitive systems like Windows.

1. What operating system do you use?

Windows 10 Enterprise

2. What version of Vagrant are you running?

2.2

3. Are you using VirtualBox or VMWare and which version are you using?

VirtualBox v6

4. Do you have a custom YAML file? If so, what does it contain?
   (Please paste in your chassis.local.yaml file)

5. Do you have any Chassis other extensions installed? If so, what are they?

Altis platform extension

[BronsonQuick]

On Windows by default only administrators can create symlinks. I think if you start VirtualBox or the terminal as administrator you won't hit this issue? I can't confirm as I don't have a Windows machine anymore ☠️

[roborourke]

@BronsonQuick for a bit more context the developers hitting this issue can only run gitbash in "elevated privileges" mode, they can't do anything as administrator so we're a bit hamstrung there if that's the case. Either way the extension paths get reported incorrectly and Chassis seems to try and clone down the extensions every time.

I think the symlinks are being created but we have an additional bug in Altis Local Chassis as a result of running vagrant commands via a PHP process. That's a separate issue though.

Cheers for the input but no expectation for you to jump in and fix this one, it's on us.