Fixed 404'ed link (#9295)

* Fixed 404'ed link

Fixed link and some minor formatting.

* Pointed to actual provider

* Typo'ed link :(
This commit is contained in:
James Turnbull 2016-10-09 12:19:55 -04:00 committed by Radek Simko
parent 28cbd48cd3
commit 467d52f964
1 changed files with 6 additions and 5 deletions

View File

@ -49,13 +49,13 @@ resource "aws_instance" "web" {
The following arguments are supported:
* `source` - This is the source file or folder. It can be specified as relative
to the current working directory or as an absolute path. This cannot be provided with `content`.
to the current working directory or as an absolute path. This attribute cannot be specifed with `content`.
* `content` - This is the content to copy on the destination. If destination is a file,
the content will be written on that file, in case of a directory a file named
*tf-file-content* is created. It's recommended to use a file as destination. A
[`template_file`](/docs/providers/template/r/file.html) might be referenced in here, or
any interpolation syntax for that matter. This cannot be provided with `source`.
[`template_file`](/docs/providers/template/d/file.html) might be referenced in here, or
any interpolation syntax. This attribute cannot be specified with `source`.
* `destination` - (Required) This is the destination path. It must be specified as an
absolute path.
@ -81,5 +81,6 @@ of `/foo` on the local machine will be uploaded to `/tmp/foo` on the remote mach
If the source, however, is `/foo/` (a trailing slash is present), and the destination is
`/tmp`, then the contents of `/foo` will be uploaded directly into `/tmp` directly.
This behavior was adopted from the standard behavior of rsync. Note that under the covers,
rsync may or may not be used.
This behavior was adopted from the standard behavior of rsync.
**Note:** Under the covers, rsync may or may not be used.