From bf31ea38d2529dafb64be80562a50f6a79095790 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?St=C3=A5le=20Johnsen?=
 <98233333+stalejohnsen@users.noreply.github.com>
Date: Sat, 30 Dec 2023 18:23:51 +0100
Subject: [PATCH] Additional Accelerator upgrade guidance (#708)

* Upgrade guidance added

* Fix trailing whitespace

* fix code language
---
 docs/wiki/Accelerator.md | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/docs/wiki/Accelerator.md b/docs/wiki/Accelerator.md
index 26ba424f2..c6871a8d9 100644
--- a/docs/wiki/Accelerator.md
+++ b/docs/wiki/Accelerator.md
@@ -228,8 +228,15 @@ With the ALZ Accelerator framework, we have designed the pipelines and directory
     ```powershell
     Get-ALZGithubRelease -i "bicep" -v "v0.17.0" -o "C:\Repos\ALZ\accelerator"
     ```
-
+    Verify that the cmdlet has updated the environment variables file (.env):
+    ```bash
+    UPSTREAM_RELEASE_VERSION="v0.17.0"
+    ```
 1. You can now deploy the updated modules.
+    > **Note:**
+    > The current pipelines trigger What-If deployment in PRs for changes in the Bicep parameter files. If you also want to include the What-If deployment process in the module upgrade process, consider the following options:
+    > - Adding the environment variables file (.env) as an additional trigger in the module pipelines
+    > - Introducing inputs/parameters in the module pipelines so you can manually trigger What-If deployments in a controlled manner.
 
 ### Incorporating Modified ALZ Modules