Revert "docs: deactivate var-file section"

This reverts commit 4ad0a882ec5f3ced986a058b17e5199a23940b45.

website/pages/docs/job-specification/hcl2/variables.mdx

@@ -158,6 +158,7 @@ maintainers, use comments.
 Once a variable is declared in your configuration, you can set it:
 
 - Individually, with the `-var foo=bar` command line option.
+- In variable definitions files specified on the command line (with `-var-file=input.vars`).
 - As environment variables, for example: `NOMAD_VAR_foo=bar`
 
 The following sections describe these options in more detail.
@@ -178,9 +179,6 @@ you at least set a default type instead of using empty blocks; this helps the
 HCL parser understand what is being set. Otherwise, the interpreter will assume
 that any variable set on the command line is a string.
 
-<!---
-# TODO (hcl2): Renable for 1.0.1 by reverting the comment out commit
-
 ### Variable Definitions Files
 
 To set lots of variables, it is more convenient to specify their values in a
@@ -211,7 +209,6 @@ corresponding to variable names:
   "labels": ["testing", "internal"],
 }
 ```
---->
 
 ### Environment Variables
 
@@ -271,7 +268,7 @@ Nomad loads variables in the following order, with later sources taking
 precedence over earlier ones:
 
 - Environment variables (lowest priority)
-- Any `-var` options on the command line, in the order they are
+- Any `-var` and `-var-file` options on the command line, in the order they are
   provided. (highest priority)
 
 If the same variable is assigned multiple values using different mechanisms,
@@ -300,3 +297,4 @@ this behavior optional :
 |            var.foo              | error, "foo needs to be set" |      null        |        xy        |
 | `NOMAD_VAR_foo=yz`<br />var.foo |              yz              |        yz        |        yz        |
 |  `-var foo=yz`<br />var.foo     |              yz              |        yz        |        yz        |
+