-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Salt Version configurable in Windows Guest #5849
Comments
Hi @obestwalter We would gladly review a Pull Request for this functionality. Thanks! |
Sounds good - I am neither experienced in Ruby nor in Powershell, though. And I guess changes are needed in both parts to be able to pass settings from the Vagrantfile to the PS script, like it is possible already with Linux guests. So it would be necessary to introduce this mechanism for Windows guests first. Am I correct? I am definitiely willing to give it a shot with a little help. So two questions:
Thanks! |
This looks to add the functionality requested: #5892 |
@PatOShea Woohoo!!! P.S. I would still very much appreciate pointers to my questions above. I had no luck on the maiing list either. |
Resolved since 1.7.4 |
At the moment version and location are hardcoded.
https://github.com/mitchellh/vagrant/blob/master/plugins/provisioners/salt/bootstrap-salt.ps1#L2
https://github.com/mitchellh/vagrant/blob/master/plugins/provisioners/salt/bootstrap-salt.ps1#L26
It would be very good to decouple the lifecycles of both projects and for cross project development/debugging.
It should be possible to set the installer location to an URL or a UNC path or a local path.
To use a mapped salt develpoment version it would be good to be able to completely skip the bootstrap step if this is not already possible but to use the mapped development version instead (I don't know exactly yet if this makes sense and how it would work - I am pretty much at the beginning to start debugging and fixing problems that touch on both projects - see also here and especially here).
The text was updated successfully, but these errors were encountered: