fix linting

Author: wellsiau-aws

examples/demo_workspace/.header.md

@@ -14,7 +14,7 @@ Follow the steps below to attach the run task created from the module into a new
 
 * Change the org name in with your own Terraform Cloud org name.
 
-  ```
+  ```hcl
   terraform {
 
     cloud {
@@ -29,6 +29,7 @@ Follow the steps below to attach the run task created from the module into a new
   ```
 
 * Populate the required variables, change the placeholder value below.
+
   ```bash
   echo 'tfc_org="<enter your org name here>"' >> tf.auto.tfvars
   echo 'aws_region="<enter the AWS region here>"' >> tf.auto.tfvars
@@ -37,6 +38,7 @@ Follow the steps below to attach the run task created from the module into a new
   ```
 
 * Initialize Terraform Cloud. When prompted, enter the name of the new demo workspace as you specified in the previous step.
+
   ```bash
   terraform init
   ```
@@ -46,29 +48,31 @@ Follow the steps below to attach the run task created from the module into a new
 * In order to create and configure the run tasks, you also need to have Terraform Cloud token stored as Variable/Variable Sets in the workspace. Add `TFE_HOSTNAME` and `TFE_TOKEN` environment variable to the same variable set or directly on the workspace.
 ![TFC Configure Variable Set](../diagram/TerraformCloud-VariableSets.png?raw=true "Configure Terraform Cloud Variable Set")
 
- * Enable the flag to attach the run task to the demo workspace.
+* Enable the flag to attach the run task to the demo workspace.
+
    ```bash
    echo 'flag_attach_runtask="true"' >> tf.auto.tfvars
    terraform apply
    ```
 
-* Navigate back to Terraform Cloud, locate the new demo workspace and confirm that the Run Task is attached to the demo workspace. 
+* Navigate back to Terraform Cloud, locate the new demo workspace and confirm that the Run Task is attached to the demo workspace.
 ![TFC Run Task in Workspace](../../diagram/TerraformCloud-RunTaskWorkspace.png?raw=true "Run Task attached to the demo workspace")
 
-
 ## Test IAM Access Analyzer using Run Task
 
 The following steps deploy simple IAM policy with invalid permissions. This should trigger the Run Task to send failure and stop the apply.
 
 * Enable the flag to deploy invalid IAM policy to the demo workspace.
+
   ```bash
   echo 'flag_deploy_invalid_resource="true"' >> tf.auto.tfvars
   ```
 
 * Run Terraform apply again
+
   ```bash
   terraform apply
   ```
 
-* Terraform apply will fail due to several errors, use the CloudWatch link to review the errors. 
-![TFC Run Task results](../../diagram/TerraformCloud-RunTaskOutput.png?raw=true "Run Task output with IAM Access Analyzer validation")
+* Terraform apply will fail due to several errors, use the CloudWatch link to review the errors.
+![TFC Run Task results](../../diagram/TerraformCloud-RunTaskOutput.png?raw=true "Run Task output with IAM Access Analyzer validation")

examples/module_workspace/.header.md

@@ -3,6 +3,7 @@
 First step is to deploy the module into dedicated Terraform Cloud workspace. The output `runtask_id` is used on other Terraform Cloud workspace to configure the runtask.
 
 * Build and package the Lambda files using the makefile. Run this command from the root directory of this repository.
+
   ```bash
   make all
   ```
@@ -15,7 +16,7 @@ First step is to deploy the module into dedicated Terraform Cloud workspace. The
 
 * Change the org name to your TFC org.
 
-  ```
+  ```hcl
   terraform {
 
     cloud {
@@ -30,6 +31,7 @@ First step is to deploy the module into dedicated Terraform Cloud workspace. The
   ```
 
 * Initialize Terraform Cloud. When prompted, enter a new workspace name, i.e. `aws-ia2-infra`
+
   ```bash
   terraform init
   ```
@@ -40,9 +42,10 @@ First step is to deploy the module into dedicated Terraform Cloud workspace. The
 
 * In order to create and configure the run tasks, you also need to have Terraform Cloud token stored as Environment Variables. Add `TFE_HOSTNAME` and `TFE_TOKEN` environment variable.
 
-* Run Terraform apply 
+* Run Terraform apply
+
   ```bash
   terraform apply
   ```
 
-* Use the output value `runtask_id` when deploying the demo workspace. See example of [demo workspace here](../demo_workspace/README.md)
+* Use the output value `runtask_id` when deploying the demo workspace. See example of [demo workspace here](../demo_workspace/README.md)