Merge branch 'master' into feature/fast-cicd-github-enable-populating-of-data-directory-sample-files-and-update-dependencies

fast/stages-multitenant/0-bootstrap-tenant/README.md

@@ -81,6 +81,12 @@ ln -s ~/fast-config/tfvars/1-resman.auto.tfvars.json ./
 
 As shown in the script output above, the provider file is a template used as a source for potentially multiple tenant installations, so it needs to be specifically configured for this tenant by setting the backend `prefix` to a unique string so that the Terraform state file will not overlap with other tenants. Open it in an editor and perform the change before proceeding.
 
+Note that the `outputs_location` variable is disabled by default, you need to explicitly set it in your `terraform.tfvars` file if you want output files to be generated by this stage. This is a sample `terraform.tfvars` that configures it, refer to the [org-level bootstrap stage documentation](../../stages/0-bootstrap/README.md#output-files-and-cross-stage-variables) for more details:
+
+```hcl
+outputs_location = "~/fast-config"
+```
+
 ### Global overrides
 
 The globals variable file linekd above contains definition which were set for the organization, for example the locations used for log sink destinations. These might not be correct for each tenant, so this stage allows overriding them via the tenant configuration variable described in the next section.

fast/stages-multitenant/1-resman-tenant/README.md

@@ -114,6 +114,12 @@ ln -s ~/fast-config/tenants/tn0/tfvars/0-bootstrap-tenant.auto.tfvars.json ./
 
 Once that is done, stage-level configuration variables are the same as the corresponding organization-level stage.
 
+Note that the `outputs_location` variable is disabled by default, you need to explicitly set it in your `terraform.tfvars` file if you want output files to be generated by this stage. This is a sample `terraform.tfvars` that configures it, refer to the [org-level bootstrap stage documentation](../../stages/0-bootstrap/README.md#output-files-and-cross-stage-variables) for more details:
+
+```hcl
+outputs_location = "~/fast-config"
+```
+
 ### Running the stage
 
 Once the configuration is done just go through the usual `init/apply` cycle. On successful apply, a tfvars file specific for this tenant and a set of provider files will be created.

fast/stages/1-resman/README.md

@@ -110,6 +110,12 @@ Variables in this stage -- like most other FAST stages -- are broadly divided in
 
 The latter set is explained in the [Customization](#customizations) sections below, and the full list can be found in the [Variables](#variables) table at the bottom of this document.
 
+Note that the `outputs_location` variable is disabled by default, you need to explicitly set it in your `terraform.tfvars` file if you want output files to be generated by this stage. This is a sample `terraform.tfvars` that configures it, refer to the [bootstrap stage documentation](../0-bootstrap/README.md#output-files-and-cross-stage-variables) for more details:
+
+```hcl
+outputs_location = "~/fast-config"
+```
+
 ### Running the stage
 
 Once provider and variable values are in place and the correct user is configured, the stage can be run:

fast/stages/2-networking-a-peering/README.md

@@ -251,6 +251,12 @@ Variables in this stage -- like most other FAST stages -- are broadly divided in
 
 The latter set is explained in the [Customization](#customizations) sections below, and the full list can be found in the [Variables](#variables) table at the bottom of this document.
 
+Note that the `outputs_location` variable is disabled by default, you need to explicitly set it in your `terraform.tfvars` file if you want output files to be generated by this stage. This is a sample `terraform.tfvars` that configures it, refer to the [bootstrap stage documentation](../0-bootstrap/README.md#output-files-and-cross-stage-variables) for more details:
+
+```hcl
+outputs_location = "~/fast-config"
+```
+
 ### Using delayed billing association for projects
 
 This configuration is possible but unsupported and only exists for development purposes, use at your own risk:

fast/stages/2-networking-b-vpn/README.md

@@ -265,6 +265,12 @@ Variables in this stage -- like most other FAST stages -- are broadly divided in
 
 The latter set is explained in the [Customization](#customizations) sections below, and the full list can be found in the [Variables](#variables) table at the bottom of this document.
 
+Note that the `outputs_location` variable is disabled by default, you need to explicitly set it in your `terraform.tfvars` file if you want output files to be generated by this stage. This is a sample `terraform.tfvars` that configures it, refer to the [bootstrap stage documentation](../0-bootstrap/README.md#output-files-and-cross-stage-variables) for more details:
+
+```hcl
+outputs_location = "~/fast-config"
+```
+
 ### Using delayed billing association for projects
 
 This configuration is possible but unsupported and only exists for development purposes, use at your own risk:

fast/stages/2-networking-c-nva/README.md

@@ -324,6 +324,12 @@ Variables in this stage -- like most other FAST stages -- are broadly divided in
 
 The latter set is explained in the [Customization](#customizations) sections below, and the full list can be found in the [Variables](#variables) table at the bottom of this document.
 
+Note that the `outputs_location` variable is disabled by default, you need to explicitly set it in your `terraform.tfvars` file if you want output files to be generated by this stage. This is a sample `terraform.tfvars` that configures it, refer to the [bootstrap stage documentation](../0-bootstrap/README.md#output-files-and-cross-stage-variables) for more details:
+
+```hcl
+outputs_location = "~/fast-config"
+```
+
 ### Using delayed billing association for projects
 
 This configuration is possible but unsupported and only exists for development purposes, use at your own risk:

fast/stages/2-networking-d-separate-envs/README.md

@@ -213,6 +213,12 @@ Variables in this stage -- like most other FAST stages -- are broadly divided in
 
 The latter set is explained in the [Customization](#customizations) sections below, and the full list can be found in the [Variables](#variables) table at the bottom of this document.
 
+Note that the `outputs_location` variable is disabled by default, you need to explicitly set it in your `terraform.tfvars` file if you want output files to be generated by this stage. This is a sample `terraform.tfvars` that configures it, refer to the [bootstrap stage documentation](../0-bootstrap/README.md#output-files-and-cross-stage-variables) for more details:
+
+```hcl
+outputs_location = "~/fast-config"
+```
+
 ### Using delayed billing association for projects
 
 This configuration is possible but unsupported and only exists for development purposes, use at your own risk:

fast/stages/2-security/README.md

@@ -108,6 +108,12 @@ Variables in this stage -- like most other FAST stages -- are broadly divided in
 
 The latter set is explained in the [Customization](#customizations) sections below, and the full list can be found in the [Variables](#variables) table at the bottom of this document.
 
+Note that the `outputs_location` variable is disabled by default, you need to explicitly set it in your `terraform.tfvars` file if you want output files to be generated by this stage. This is a sample `terraform.tfvars` that configures it, refer to the [bootstrap stage documentation](../0-bootstrap/README.md#output-files-and-cross-stage-variables) for more details:
+
+```hcl
+outputs_location = "~/fast-config"
+```
+
 ### Using delayed billing association for projects
 
 This configuration is possible but unsupported and only exists for development purposes, use at your own risk: