Commit Graph

20 Commits

Author SHA1 Message Date
Paul Hinze a7cbbbd258 communicator/ssh: bastion host support
* adds `bastion_*` fields to `connection` which add configuration for a
   bastion host
 * if `bastion_host` is set, connect to that host first, then jump
   through it to make the SSH connection to `host`
 * enables SSH Agent forwarding by default
2015-06-22 18:00:18 -05:00
Paul Hinze 44de0996c5 communicator/ssh: switch agent default to true
This changes SSH Agent utilization from opt-in to opt-out, bringing
Terraform in line with the behavior of Packer and the `ssh` command
itself.

But skip SSH agent connections if the SSH_AUTH_SOCK env var doesn't exist,
whcih means there's no agent to connect to.
2015-06-19 17:14:43 -05:00
Sander van Harmelen 0e87980c72 provisioner/chef: small fix in the docs 2015-05-18 16:21:31 +02:00
Sander van Harmelen 11314a3d71 Tweaking a few minor things according to the feedback on GH 2015-05-12 10:37:38 +02:00
Sander van Harmelen c19d92fb67 Refactored quite a few things after review...
Also renamed the provisioner to just `chef` as it’s out intention to
end up with one provisioner for all types of `chef` clients.
2015-05-08 23:25:24 +02:00
Sander van Harmelen 60984b2da2 This commit adds a Chef Client provisioner
The commit is pretty complete and has a tested/working provisioner for
both SSH and WinRM. There are a few tests, but we maybe need another
few to have better coverage. Docs are also included…
2015-05-08 14:54:56 +02:00
Sander van Harmelen 907eee24f2 Updating the docs 2015-05-01 18:50:57 +02:00
Paul Thrasher b7683d1a39 Typo in website docs for remote-exec
Just a simple typo fix.
2015-04-22 15:00:16 -07:00
Mitchell Hashimoto 5f4e2d9b27 website: clarify script args [GH-236] 2015-04-22 09:03:38 +02:00
Tarrant 951f4201f7 Add documentation for ssh-agent 2015-03-15 16:37:33 -07:00
Mitchell Hashimoto 577e2420b0 Revert "docs: consistent use of array configuration syntax"
This reverts commit 4893eb8b55.
2015-01-14 09:28:25 -08:00
Emil Hessman 4893eb8b55 docs: consistent use of array configuration syntax
The Terraform configuration syntax defines what arrays are.
Use the word array consistently throughout the documentation
instead of list.

The corresponding JSON datatype is called array as well, and
since the Terraform configuration syntax is interoperable with
JSON it makes sense to use the term array to describe them.
2015-01-13 06:59:12 +01:00
Seth Vargo 073a0f76c5 Add meta descriptions to all pages 2014-10-21 23:21:56 -04:00
Armon Dadgar fc324464b8 website: Fixing typo 2014-09-30 11:41:58 -07:00
Tushar Pokle 7ff36710a6 Fixed example
The cat should actually be an echo if you want to write the IP address to a file
2014-07-30 21:56:02 +10:00
borgified b5590ee6da spellchecked all the *.markdown
ran this command:
find . -iname *.markdown -type f -exec aspell check {} \;
and manually checked each problem that aspell found
2014-07-28 23:51:24 -07:00
Armon Dadgar 10383cfc67 website: Change local-exec example 2014-07-27 15:41:08 -04:00
Armon Dadgar e2aeacc8d2 website: Fixing typo 2014-07-24 14:40:34 -04:00
Armon Dadgar ae1fc27cc0 website: AWS Provider 2014-07-23 15:14:35 -04:00
Armon Dadgar 93caf16b4c website: Document provisioners 2014-07-23 12:40:19 -04:00