ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Added example of how the Option settings works (#8413) 

It took me some googling to find this and thought it would be good to have an example of how that structure is meant to be right in the docs.
This commit is contained in:
Adam Dehnel 2016-08-23 08:47:10 -05:00 committed by Paul Stack
parent c853eb5525
commit 6f3fd1faa0
1 changed files with 27 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
website/source/docs/providers/aws/r/elastic_beanstalk_environment.html.markdown
View File

@ -76,6 +76,32 @@ The `setting` and `all_settings` mappings support the following format:
* `value` - value for the configuration option * `value` - value for the configuration option
* `resource` - (Optional) resource name for [scheduled action](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-autoscalingscheduledaction) * `resource` - (Optional) resource name for [scheduled action](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-autoscalingscheduledaction)
### Example With Options
```
resource "aws_elastic_beanstalk_application" "tftest" {
name = "tf-test-name"
description = "tf-test-desc"
}
resource "aws_elastic_beanstalk_environment" "tfenvtest" {
name = "tf-test-name"
application = "${aws_elastic_beanstalk_application.tftest.name}"
solution_stack_name = "64bit Amazon Linux 2015.03 v2.0.3 running Go 1.4"
setting {
namespace = "aws:ec2:vpc"
name = "VPCId"
value = "vpc-xxxxxxxx"
}
setting {
namespace = "aws:ec2:vpc"
name = "Subnets"
value = "subnet-xxxxxxxx"
}
}
```
## Attributes Reference ## Attributes Reference
The following attributes are exported: The following attributes are exported: