Merge pull request #59 from magnus-longva-bouvet/patch-1

"VERBOSE" instead of "TRACE"

website/docs/rover/commands.md

@@ -64,7 +64,7 @@ The following table summarizes the most common parameters and their default valu
 | -env                              | yes      | N/A                                                                                                | String that defines a name for an environment to use. This is defined as  (used in the state locator function as described below.)                                                                                                                                                            | ```contoso```                                                          |
 | -level                            | yes      | N/A                                                                                                | Specifies the level in the CAF hierarchy where to deploy the resources (possible value are level1-level4)                                                                                                                                                                                     | ```level1```                                                           |
 | -a                                | yes      | N/A                                                                                                | Action to take with the current parameters, possible values are ```plan```, ```apply```, ```destroy```, ```validate```, ```refresh```, ```graph```, ```import```, ```output```, ```taint```, ```untaint```, ```'state list'```, ```'state rm'```, ```'state show'```                          | ```plan```                                                             |
-| -log-severity                     | no       | ERROR                                                                                              | Specifies the Terraform log verbosity this sets the ```TF_IN_AUTOMATION``` parameters, possible options are: ```TRACE```, ```DEBUG```, ```INFO```, ```WARN``` or ```ERROR```                                                                                                                  | ```ERROR```                                                            |
+| -log-severity                     | no       | ERROR                                                                                              | Specifies the Terraform log verbosity this sets the ```TF_IN_AUTOMATION``` parameters, possible options are: ```VERBOSE```, ```DEBUG```, ```INFO```, ```WARN``` or ```ERROR```                                                                                                                  | ```ERROR```                                                            |
 | -tfstate_subscription_id          | no       | If no value specified, rover is assuming the currently logged-in subscription from az cli context. | GUID of the subscription containing the tfstate (launchpad). This will be used to locate and store the tfstate files.                                                                                                                                                                         | ```a-b-c-d-e  ```                                                      |
 | -target_subscription              | no       | If no value specified, rover is assuming the currently logged-in subscription from az cli context. | GUID of the subscription where to deploy the resources.                                                                                                                                                                                                                                       | ```a-b-c-d-e```                                                        |
 | -workspace                        | no       | ```tfstate```                                                                                      | Specifies the storage account container where to store the tfstate for this landing zone. This could be used to isolate landing zones from each others by specifying Azure AD RBAC entries on the specific container withing the storage account.                                             | ```my_container```                                                     |