From 15e42ac93937a41b1516b42bab4440deda5ca556 Mon Sep 17 00:00:00 2001 From: James Turnbull Date: Tue, 25 Oct 2016 06:56:33 -0400 Subject: [PATCH] Added provider to meta-param resource docs I am not sure `provider` IS a meta-param but it looks like one... --- website/source/docs/configuration/resources.html.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/website/source/docs/configuration/resources.html.md b/website/source/docs/configuration/resources.html.md index e69b3561f..e9ebb3b5d 100644 --- a/website/source/docs/configuration/resources.html.md +++ b/website/source/docs/configuration/resources.html.md @@ -41,6 +41,7 @@ configuration is dependent on the type, and is documented for each resource type in the [providers section](/docs/providers/index.html). + ### Meta-parameters There are **meta-parameters** available to all resources: @@ -55,6 +56,11 @@ There are **meta-parameters** available to all resources: resource. The dependencies are in the format of `TYPE.NAME`, for example `aws_instance.web`. + * `provider` (string) - The name of a specific provider to use for + this resource. The name is in the format of `TYPE.ALIAS`, for example, + `aws.west`. Where `west` is set using the `alias` attribute in a + provider. See [multiple provider instances](#multi-provider-instances). + * `lifecycle` (configuration block) - Customizes the lifecycle behavior of the resource. The specific options are documented below. @@ -90,6 +96,8 @@ which will match all attribute names. Using a partial string together with a wildcard (e.g. `"rout*"`) is **not** supported. + + ### Connection block Within a resource, you can optionally have a **connection block**. @@ -105,6 +113,8 @@ but other data must be specified by the user. The full list of settings that can be specified are listed on the [provisioner connection page](/docs/provisioners/connection.html). + + ### Provisioners Within a resource, you can specify zero or more **provisioner @@ -151,6 +161,8 @@ resource "aws_instance" "app" { } ``` + + ## Multiple Provider Instances By default, a resource targets the provider based on its type. For example