From f3f0b5356e4f3f6c1043cc9cdc6a1d6371e8d667 Mon Sep 17 00:00:00 2001 From: Martin Atkins Date: Thu, 16 Nov 2017 10:14:03 -0800 Subject: [PATCH] website: specify HCL syntax highlighting in the 0.11 upgrade guide --- website/upgrade-guides/0-11.html.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/upgrade-guides/0-11.html.markdown b/website/upgrade-guides/0-11.html.markdown index fc33ed02b..890d7df3f 100644 --- a/website/upgrade-guides/0-11.html.markdown +++ b/website/upgrade-guides/0-11.html.markdown @@ -172,7 +172,7 @@ all of the module's resources can be successfully refreshed and destroyed. A common configuration is where two child modules have different configurations for the same provider, like this: -``` +```hcl # root.tf module "network-use1" { @@ -186,7 +186,7 @@ module "network-usw2" { } ``` -``` +```hcl # network/network.tf variable "region" { @@ -212,7 +212,7 @@ This can be addressed by moving the `provider` blocks into the root module as _additional configurations_, and then passing them down to the child modules as _default configurations_ via the explicit `providers` map: -``` +```hcl # root.tf provider "aws" { @@ -242,7 +242,7 @@ module "network-usw2" { } ``` -``` +```hcl # network/network.tf # Empty provider block signals that we expect a default (unaliased) "aws"