Sander van Harmelen 68c6835bb5 Do not create a random public port (#4149) ... This is meant to be a gentle solution for a very specific use case, but is causing more issues then it solves. If you have a port conflict when trying to use an already associated public IP, the easiest way around it is to let the builder associate a new temporary public IP address.		2016-11-10 13:59:58 +01:00
..
amazon	fix go vet issue.	2016-11-07 10:17:53 -08:00
azure	Merge pull request #3996 from boumenot/pr-issue-3968	2016-10-13 13:39:54 -07:00
cloudstack	Do not create a random public port (#4149)	2016-11-10 13:59:58 +01:00
digitalocean	run gofmt	2016-11-01 14:08:04 -07:00
docker	aws-sdk: use session.NewSession	2016-11-01 15:53:04 -07:00
file	…
googlecompute	Merge pull request #4101 from lwander/f-googlecompute-ssh-private-key-file	2016-11-03 11:04:02 -07:00
null	…
openstack	builder/openstack: Support using SSH password.	2016-10-08 23:18:19 +02:00
parallels	run gofmt	2016-11-01 14:08:04 -07:00
profitbricks	run gofmt	2016-11-01 14:08:04 -07:00
qemu	Fix keycodes for ctrl,shift and alt key when sending over VNC	2016-11-04 19:26:14 +09:00
virtualbox	run gofmt	2016-11-01 14:08:04 -07:00
vmware	Fix keycodes for ctrl,shift and alt key when sending over VNC	2016-11-04 19:26:14 +09:00