- Rename buildpacker to buildlab, since it's not just a packer thing
- Clean up hardcoded crap and references to (the old Python version of)
caryatid from buildlab
- Delete code as much as possible, shortening file by ~30%
- Minor readme cleanup
baseconfigname The name of one of the subdirs of the 'packer'
directory, like windows_81_x86
optional arguments:
-h, --help show this help message and exit
--base-out-dir BASE_OUT_DIR, -o BASE_OUT_DIR
The base output directory, where Packer does its work
and saves its final output. (NOT the VM directory,
which is a setting in VirtualBox.)
--action {packer,vagrant,packervagrant}, -a {packer,vagrant,packervagrant}
The action to perform. By default, build with packer
and add to vagrant.
--whatif, -w Do not perform any actions, only say what would have
been done
--force, -f Force continue, even if old output directories already
exist
--verbose, -v Print verbose messages
NOTE: requires packer 0.8.6 or higher and vagrant 1.8 or higher. EXAMPLE:
buildlab --baseconfigname windows_10_x86; cd vagrant/FreyjaA; vagrant up
Note that doing the actual `vagrant up` is not part of buildlab - it only makes the box available for you to `vagrant up` later. See my example Vagrant boxes in the vagrant subdirectory, but note that these will be specific to my use; you'll probably want to define your own Vagrantfile(s) with your own provisioner scripts.
## Credits
This started as some customizations for [joefitzgerald/packer-windows](https://github.com/joefitzgerald/packer-windows) that got a liiiiiiiittle out of hand.
@ -42,11 +85,6 @@ And these are some specific changes that may impact you
## To do
buildlab.ps1 improvements:
- would like to use the -tag in the name for the vagrant box too, but that requires parameterizing both the packerfile and the vagrantfile template :/ not sure what to do about this
- I have a concept of "packer basename" and "tag" in buildlab. Extend this to also have "architecture" and "flavor" (or something - to capture Server Standard vs Core vs Datacenter etc)
packer/vagrant/postinstall improvements:
- store passwords securely for shit and/or generate them on the fly
@ -78,4 +116,3 @@ upstream improvements
- The original packer-windows crew got aroudn this by using the `Run` key and disabling UAC in `Autounattend.xml`
- I'm planning to get around this by creating a scheduled task that starts at boot and runs with highest privileges. This won't work pre-Vista/2008, but that's OK with me.
- This means I need to write an executor that can start at boot, and then check for things to execute located elsewhere. Bleh.