Commit Graph

6 Commits

Author SHA1 Message Date
Max Riveiro
137fcfb5de Massively add HCL source tag in docs Markdown files
Signed-off-by: Max Riveiro <kavu13@gmail.com>
2017-04-17 13:17:54 +03:00
Paul Stack
67f02e6a54 provider/aws: Documentation fixes for aws_ami (#13694)
* provider/aws: Documentation fixes for aws_ami

Fixes: #13685

* Update ami.html.markdown
2017-04-17 01:33:30 +03:00
George Christou
61277c0dbd website/docs: Run terraform fmt on code examples (#12075)
* docs/vsphere: Fix code block

* docs: Convert `...` to `# ...` to allow `terraform fmt`ing

* docs: Trim trailing whitespace

* docs: First-pass run of `terraform fmt` on code examples
2017-02-19 00:48:50 +02:00
Brad Sickles
732b8d3b6e Implementing aws_ami_launch_permission. (#7365) 2016-07-21 23:08:32 +01:00
Paul Stack
58c324676d provider/aws: Add support for encryption and kms_key_id to aws_ami (#7181)
This fixes #7157. It doesn't change the way aws_ami works

```
make testacc TEST=./builtin/providers/aws
TESTARGS='-run=TestAccAWSAMICopy'
==> Checking that code complies with gofmt requirements...
go generate $(go list ./... | grep -v /vendor/)
TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSAMICopy
-timeout 120m
=== RUN   TestAccAWSAMICopy
--- PASS: TestAccAWSAMICopy (479.75s)
PASS
ok      github.com/hashicorp/terraform/builtin/providers/aws    479.769s
```
2016-07-05 09:50:48 -05:00
Martin Atkins
7f64327663 Three resources for AWS AMIs.
AWS provides three different ways to create AMIs that each have different
inputs, but once they are complete the same management operations apply.

Thus these three resources each have a different "Create" implementation
but then share the same "Read", "Update" and "Delete" implementations.
2015-09-03 10:05:41 -07:00