Update GCE source_image to debian-7-wheezy-v20140415
Added documentation page for environmental variables. #1130
Changed the ordering of the environmental variables to be alphabetic.
Add option to enable enhanced networking (SriovNetSupport) for images.
Docs updated with new config option
Fixes #1244, Add a check for upload iso hash to ESXi Driver
Hyper-V support added
[GCE] gsutil update fails in newer images, use gcloud

    googlecompute: It looks like you are trying to run "/usr/local/bin/../share/google/google-cloud-sdk/bin/bootstrapping/gsutil.py update".
    googlecompute: The "update" command is no longer needed with the Cloud SDK.
    googlecompute: To update, run: gcloud components update
Accept VirtualBox release candidate version (ex. 4.3.14_RC1 from 4.3.14_RC1r94870)
tested VMware and VirtualBox fixes
pulled in host_ip from wrong place
Changed to reflect the new httpS endpoint for Chef, since Chef 11.x
Merge pull request #1340 from tehmaspc/tehmaspc_chefserver_https_endpoint_doc_update

[DOC] Changed to reflect the new httpS endpoint for Chef, since Chef 11.x
amazon builders now handle templating of user_data and user_data_file
null-builder: added support for templating
Cleaned up Go formatting with gofmt.
Fixed typo
Fixed Rackspace example

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?
Problem:

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.
Problem: Docs should mention the comma after `"builders": [...]`

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.