-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Allow remote OVF downloads #1195
Comments
So each team member needs to run provision steps that are unique to that team member? |
+1 for this. It would be nice not to need something external to Packer to download the image. |
This sounds good to me. Tagged. |
+1 |
2 similar comments
+1 |
+1 |
I think this should be fairly easy to do with go-getter, which can support getting all the bits out of a zip file. |
+1 |
To @cbednarski's point, what would the implementation of this look like? I could see |
@artburkart I think for the ovf case we would say it must be in a tar or zip, and it will be extracted after we download it. You're right though that without an archive of some kind there is no way to know which files are supposed to be included. |
Any plans to allow for remote ovf file downloads with an ovf_url, along with the corresponding vmdk, as you did with iso_url?
I want to send the team a packer config that uses a hosted ovf base box, makes some customizations using provisioning scripts, and then builds a Vagrant box.
The text was updated successfully, but these errors were encountered: