Commit Graph

7633 Commits

Author SHA1 Message Date
Rickard von Essen 69daca2a33 Merge pull request #4934 from jasonramey/master
spelling fix
2017-05-26 07:07:25 +02:00
Jason Ramey cc309c0e5f spelling fix 2017-05-26 01:03:11 -04:00
Matthew Hooker 0e3469e913
spell fix 2017-05-25 18:49:45 -07:00
Matthew Hooker 74b20f69ce
update changelog 2017-05-25 14:21:09 -07:00
Matthew Hooker c436d9aea4 Merge pull request #4931 from hashicorp/fix4817
only delete snapshots which exist
2017-05-25 14:19:40 -07:00
Matthew Hooker 77b4d47409
only delete snapshots which exist 2017-05-25 14:16:20 -07:00
Matthew Hooker 1cf4754d80
correct ami_name error reporting 2017-05-25 13:02:36 -07:00
Matthew Hooker 96232790b9
update changelog 2017-05-25 10:30:57 -07:00
Matthew Hooker ceb180668f Merge pull request #4927 from jen20/vmware-remove-ethernet
builder/vmware: Add vmx_remove_ethernet_interfaces
2017-05-25 10:28:58 -07:00
James Nugent c4439aba82 builder/vmware: Add vmx_remove_ethernet_interfaces
This commit adds a new option, `vmx_remove_ethernet_interfaces`, to both
of the VMWare builders. This is useful when building Vagrant boxes,
since Vagrant now produces output such as:

```
WARNING: The VMX file for this box contains a setting that is
automatically overwritten by Vagrant when started. Vagrant will stop
overwriting this setting in an upcoming release which may pre vent
proper networking setup. Below is the detected VMX setting:

   ethernet0.pcislotnumber = "33"

If networking fails to properly configure, it may require this VMX
setting. It can be manually applied via the Vagrantfile:

   Vagrant.configure(2) do |config|
     config.vm.provider :vmware_fusion do |vmware|
       vmware.vmx["ethernet0.pcislotnumber"] = "33"
     end
   end
```

This can be avoided entirely by removing the ethernet adapters from the
VMX file prior to packaging as a Vagrant box, in which case adapters are
created as expected according to the Vagrantfile specification.
2017-05-24 18:53:25 -05:00
Matthew Hooker ce40c3d708
update changelog 2017-05-24 11:10:47 -07:00
Matthew Hooker 21c4d66143 Merge pull request #4921 from takaishi/support-client-certificate
OpenStack: Support client certificate
2017-05-24 11:08:24 -07:00
Matthew Hooker f6eb4e1b40
use cleanhttp to get a default transport. 2017-05-24 11:05:59 -07:00
Matthew Hooker 392309c69d Merge pull request #4926 from hashicorp/megan_contributors_page
add Megan to contributors page
2017-05-24 10:48:47 -07:00
Megan Marsh 5687b1001d add Megan to contributors page 2017-05-24 10:26:09 -07:00
r_takaishi 4fc0616bc9 fix go vet fail 2017-05-24 17:57:21 +09:00
r_takaishi db58854b0b make fmt 2017-05-24 16:28:13 +09:00
r_takaishi 37e6539bff use DefaultTransport 2017-05-24 16:19:30 +09:00
r_takaishi 67ce2da59e add cacert config to specify custom CA certificate file 2017-05-24 14:21:16 +09:00
r_takaishi c909a27e7b fix docs 2017-05-24 14:07:12 +09:00
r_takaishi a36d9d6b44 add docs 2017-05-24 10:27:29 +09:00
r_takaishi 1de9eb2cfd support client certificate file
When AUTH_URL and each endpoints need SSL client authentication, we
have to specify cert file and private key file.
So, add optional config, cert and key.
2017-05-24 10:23:12 +09:00
Matthew Hooker 4bdba88892 Merge pull request #4918 from hashicorp/vagrant-cloud-post-processor-updates
website: Vagrant Cloud post-processor updates
2017-05-23 11:27:39 -07:00
Justin Campbell db91f94a08 website: Add Vagrant note to atlas post-processor 2017-05-23 11:21:34 -04:00
Justin Campbell e934633df9 website: Remove Vagrant from Atlas post-processor 2017-05-23 11:16:50 -04:00
Justin Campbell e554c3d8f7 website: Un-deprecate vagrant-cloud post-processor 2017-05-23 11:15:24 -04:00
Matthew Hooker d6a0068c2d
don't echo build command in make 2017-05-22 15:03:21 -07:00
Matthew Hooker aa0dbf308f
update changelog 2017-05-22 13:41:47 -07:00
Matthew Hooker 2ceaa2b79e Merge pull request #4748 from greenhouse-org/download-winrm
Add support for download in WinRM communicator
2017-05-22 13:35:25 -07:00
James Nugent afba8ebb30 Merge pull request #4911 from cheapRoc/f-note-triton
Documentation: Note for private cloud users building custom images on Triton
2017-05-21 14:46:24 -05:00
Justin Reagor edc8eabe2e Note documentation when building images under private Triton 2017-05-21 14:40:36 -04:00
Matthew Hooker 30d056d085
update changelog 2017-05-20 18:38:21 -07:00
Matthew Hooker ce5930743d Merge pull request #4909 from sean-/b-universal-shell
Universally provide POSIX semantics for the `shell` provisioner.
2017-05-20 18:34:10 -07:00
Matthew Hooker 3bf637f0d3 Merge pull request #4910 from decomposite/HostKeyCallback
Specify InsecureIgnoreHostKey for HostKeyCallback
2017-05-20 17:58:27 -07:00
JD Friedrikson a0052fdb68
Specify InsecureIgnoreHostKey for HostKeyCallback
[A recent breaking change upstream in Golang's crypto
library](e4e2799dd7)
has broken SSH connectivity for a few builders:

```
==> qemu: Waiting for SSH to become available...
2017/05/20 16:23:58 ui: ==> qemu: Waiting for SSH to become available...
2017/05/20 16:23:58 packer: 2017/05/20 16:23:58 [INFO] Attempting SSH connection...
2017/05/20 16:23:58 packer: 2017/05/20 16:23:58 reconnecting to TCP connection for SSH
2017/05/20 16:23:58 packer: 2017/05/20 16:23:58 handshaking with SSH
2017/05/20 16:23:58 packer: 2017/05/20 16:23:58 handshake error: ssh: must specify HostKeyCallback
2017/05/20 16:23:58 packer: 2017/05/20 16:23:58 [DEBUG] SSH handshake err: ssh: must specify HostKeyCallback
2017/05/20 16:24:05 packer: 2017/05/20 16:24:05 [INFO] Attempting SSH connection...
2017/05/20 16:24:05 packer: 2017/05/20 16:24:05 reconnecting to TCP connection for SSH
2017/05/20 16:24:05 packer: 2017/05/20 16:24:05 handshaking with SSH
2017/05/20 16:24:05 packer: 2017/05/20 16:24:05 handshake error: ssh: must specify HostKeyCallback
2017/05/20 16:24:05 packer: 2017/05/20 16:24:05 [DEBUG] SSH handshake err: ssh: must specify HostKeyCallback
```

Specifying HostKeyCallback as insecure should make things work again
and would make sense for packer's use case.
2017-05-20 16:17:04 -04:00
Sean Chittenden 1ba7f9cc20
Universally provide POSIX semantics for the `shell` provisioner.
All platforms everywhere have `env(1)` available, leverage it
accordingly.

Improves on: #2343
2017-05-20 09:28:02 -07:00
Matthew Hooker 740f438639
clarify that variables can't be used inside type 2017-05-20 00:53:31 -07:00
Matthew Hooker 4d84915bf8 Merge pull request #4890 from jamtur01/varrename
Updated the naming of variables
2017-05-20 00:50:27 -07:00
Matthew Hooker fdfb3fa1a6 Merge pull request #4902 from hashicorp/amivalidation
fix ami name validation
2017-05-20 00:47:54 -07:00
Matthew Hooker db9e539c6b
update changelog 2017-05-19 22:55:32 -07:00
Matthew Hooker 932c4715e7 Merge pull request #4907 from WeatherGod/invalid_json_test
test that parsing fails on a certain kind of malformed JSON
2017-05-19 13:54:05 -07:00
Ben Root 5beca186d7 Unit test to verify that parsing fails on a certain kind of malformed JSON 2017-05-19 16:42:42 -04:00
Matthew Hooker b75367204f Merge pull request #4906 from hashicorp/jsonunmarshal
use json unmarshal instead of json decoder
2017-05-19 12:04:19 -07:00
Matthew Hooker 3fe1f20770
use json unmarshal instead of json decoder
this should let us catch json syntax errors.
2017-05-19 12:02:48 -07:00
Matthew Hooker 4137660b7a
fix ami name validation 2017-05-19 02:11:43 -07:00
Matthew Hooker e67d1fd676 Merge pull request #4900 from rogers0/PR/crypto-CVE-ABI-change
handle ABI change of golang-golang-x-crypto-dev
2017-05-18 12:06:08 -07:00
Matthew Hooker ee5d13611f
update ssh client usage for new crypto/ssh version 2017-05-18 12:01:44 -07:00
Matthew Hooker 249cb690e0
update crypto/ssh 2017-05-18 12:01:29 -07:00
Matthew Hooker ef79669bef Merge pull request #4898 from numa08/master
I've matched the error message to the document
2017-05-18 10:46:54 -07:00
numa b15c3a5c92 Fix error message
I've matched the error message to the document
2017-05-18 18:40:16 +09:00