- 19 Jul, 2014 15 commits
-
-
Mitchell Hashimoto authored
website: Fixed Rackspace example
-
Mitchell Hashimoto authored
-
Mitchell Hashimoto authored
-
Mitchell Hashimoto authored
-
Mitchell Hashimoto authored
-
Mitchell Hashimoto authored
-
Mitchell Hashimoto authored
builder/vmware/esxi: checksum iso upload to not always upload
-
Mitchell Hashimoto authored
builder/virtualbox: Accept VirtualBox release candidate version
-
Mitchell Hashimoto authored
packer: Fixed typo in error message
-
Mitchell Hashimoto authored
website: Specifically call out the comma after `"builders": [...]`
-
Mitchell Hashimoto authored
-
Mitchell Hashimoto authored
Install gox during build time
-
Mitchell Hashimoto authored
post-processor/vagrant: hyper-v
-
Sudharshan S authored
Just so that we can just run `make` without installing gox separatelyy
-
Mitchell Hashimoto authored
Cleaned up Go formatting with gofmt.
-
- 18 Jul, 2014 7 commits
-
-
stefanlasiewski authored
-
stefanlasiewski authored
-
stefanlasiewski authored
-
stefanlasiewski authored
-
stefanlasiewski authored
While running through the getting-started examples, I ran into a strange error: packer $ packer validate example.json Failed to parse template: Error in line 16, char 2: invalid character '"' after object key:value pair "provisioners": [{ packer $ The error was not immediately obvious, as this is my first time working with Packer, and like many users this also happens to be my first time working with JSON. Solution: I was missing a comma after the 'builders' configuration. I'm sure this is a common problem, so let's specifically mention that in the document.
-
stefanlasiewski authored
While running through the getting-started examples, I ran into a strange error: packer $ packer validate example.json Failed to parse template: Error in line 16, char 2: invalid character '"' after object key:value pair "provisioners": [{ packer $ The error was not immediately obvious, as this is my first time working with Packer, and like many users this also happens to be my first time working with JSON. Solution: I was missing a comma after the 'builders' configuration. I'm sure this is a common problem, so let's specifically mention that in the document.
-
Kane Rogers authored
As per https://github.com/mitchellh/packer/issues/1142, it's critical to add openstack_provider: rackspace in order to get anything to work reliably with Rackspace and Packer in 6.0. Question: should the openstack_provider field now be marked as required?
-
- 17 Jul, 2014 3 commits
-
-
Tehmasp Chaudhri authored
-
Misha Brukman authored
-
Ross Smith II authored
[DOC] Changed to reflect the new httpS endpoint for Chef, since Chef 11.x
-
- 16 Jul, 2014 1 commit
-
-
Tehmasp Chaudhri authored
-
- 12 Jul, 2014 1 commit
-
-
Hiroaki Nakamura authored
-
- 11 Jul, 2014 6 commits
-
-
Jack Pearkes authored
-
Ross Smith II authored
**New post processor:** `vagrant-cloud` - Push box files generated by vagrant post processor to Vagrant Cloud. [GH-1289]
-
Ross Smith II authored
provisioner/chef-*: Fix remotePaths for Windows [GH-394]
-
Ross Smith II authored
Fix remotePaths when provisioning Linux from Windows Fixes #394
-
Ross Smith II authored
alphabetize options
-
sawanoboly authored
-
- 10 Jul, 2014 1 commit
-
-
Mitchell Hashimoto authored
Vagrant Cloud Post-Processor
-
- 05 Jul, 2014 2 commits
-
-
Ross Smith II authored
-
Ross Smith II authored
fix invalid esx5 path separator in windows
-
- 02 Jul, 2014 1 commit
-
-
yuuzi41 authored
before, this code had joining path elements by filepath module. filepath module generate path string with backslash-joined in Windows. but ESX require path string with slash-joined. it means that this code generate illegal path string in windows. illegal path string raised "Error creating disk". this patch fixes path separator from backslash to slash in windows. from this, creating disk would succeed without error.
-
- 01 Jul, 2014 2 commits
-
-
Ross Smith II authored
Replace ListServers hack with update ServerById
-
Ian Delahorne authored
[gophercloud#168](https://github.com/rackspace/gophercloud/issues/168) has been patched to not panic on non-existing server id's. If an error is returned, check if the error is a 404 first before bailing.
-
- 30 Jun, 2014 1 commit
-
-
Ross Smith II authored
builder/openstack: Workaround for gophercloud.ServerById crashing [GH-1257]
-