common/command/template,packer/template: fix build name ConfigTemplate processing [GH-858]
adding default nodename
allow none checksumtype for qemu builder (copy/paste from virtualbox)

Signed-off-by: Vasiliy Tolstov <v.tolstov@selfip.ru>
add missing variable

Signed-off-by: Vasiliy Tolstov <v.tolstov@selfip.ru>
fix digitalocean v2 api content-type when using json

In case of using json we need to set content-type header.

Signed-off-by: Vasiliy Tolstov <v.tolstov@selfip.ru>
add error code for failed auth

Signed-off-by: Vasiliy Tolstov <v.tolstov@selfip.ru>
Merge branch 'master' of github.com:vtolstov/packer into digitalocean
Merge branch 'master' of github.com:vtolstov/packer into digitalocean
website: fix SSL on downloads page
add CD-ROM only if not used disk_image, also boot from it only if CD-ROM present

Signed-off-by: Vasiliy Tolstov <v.tolstov@selfip.ru>
disk_filename is used for artifacts, but it missed in case of disk_image = true

Signed-off-by: Vasiliy Tolstov <v.tolstov@selfip.ru>
website: inherit font scheme
fix using private ip address in digitalocean builder

Signed-off-by: Vasiliy Tolstov <v.tolstov@selfip.ru>
Resolves issue where docker communicator mishandled symlinks by treating them as files
consistent escaping for ovftool uri creds

I got thrown for a loop since the username is uri-escaped but the password was not.

I got thrown for another couple of loops due to the multiple levels of interpretation involved:
1) JSON syntax requires backslashes to be slash-escaped. Some vCenter deployments use windows domain-style usernames DOMAIN\user
2) the OVFTOOL docs specify that "all special characters" be uri-encoded when part of the user name or password
3) different shell interpretations on windows/linux

I'd say escape both or neither.
Added the Ubuntu image project for GCE.

The documentation:
https://cloud.google.com/compute/docs/operating-systems#ubuntu
shows that `ubuntu-os-cloud` is the proper project name.
Merge pull request #1676 from mbrukman/gce-ubuntu

Added the Ubuntu image project for GCE.
Use golang/oauth2, no longer require client_secrets.json, and use
Service Account when run from a GCE Instance.
Merge pull request #1679 from evandbrown/gce-service-accounts

Use golang/oauth2, no longer require client_secrets.json, and use
Create GCE image from persistent disk instead of from a tarball.

The new flow:
1) Provision the instance
2) Tear down the instance, but keep the boot disk
3) Create an image from the disk
4) Tear down the disk

The step to update gcloud is no longer needed, since gceimagebundle isn't used anymore.
Fixes #1507 and addresses https://github.com/mitchellh/packer/issues/1447#issuecomment-61610235.