Merge pull request #127 from AviatrixSystems/fs-update

Flightschool update
AviatrixSystems · Jan 3, 2024 · 6b0b17d · 6b0b17d
2 parents 74fe7e1 + 4f0f358
commit 6b0b17d
Show file tree

Hide file tree

Showing 8 changed files with 4 additions and 4 deletions.
diff --git a/docs/flightschool/_images/lab1-copilot-topology.png b/docs/flightschool/_images/lab1-copilot-topology.png
diff --git a/docs/flightschool/_images/lab4-associate-existing-firewall.png b/docs/flightschool/_images/lab4-associate-existing-firewall.png
diff --git a/docs/flightschool/_sources/docs/lab4.md b/docs/flightschool/_sources/docs/lab4.md
@@ -192,7 +192,7 @@ We have already deployed a firewall instance in the lab. In order for Firenet to
 ![Associate existing firewall](images/lab4-associate-existing-firewall-add.png)  
 _Fig. Associate existing firewall_  
 
-* In the pane that opened, add the configuration as shown on the screenshot. Most information shows up when you click on the pull down menu's.
+* In the pane that opened, add the configuration as shown on the screenshot. Most information shows up when you click on the pull down menu's. Note the 6-digit suffix for the `resource group` and `firewall id` will be different than the screenshot.
 
 ![Existing firewall configuration](images/lab4-associate-existing-firewall.png)  
 _Fig. Existing firewall configuration_  

diff --git a/docs/flightschool/docs/lab4.html b/docs/flightschool/docs/lab4.html
@@ -595,7 +595,7 @@ <h3>Validate<a class="headerlink" href="#id17" title="Permalink to this heading"
 <p><img alt="Associate existing firewall" src="../_images/lab4-associate-existing-firewall-add.png" /><br />
 <em>Fig. Associate existing firewall</em></p>
 <ul class="simple">
-<li><p>In the pane that opened, add the configuration as shown on the screenshot. Most information shows up when you click on the pull down menu’s.</p></li>
+<li><p>In the pane that opened, add the configuration as shown on the screenshot. Most information shows up when you click on the pull down menu’s. Note the 6-digit suffix for the <code class="docutils literal notranslate"><span class="pre">resource</span> <span class="pre">group</span></code> and <code class="docutils literal notranslate"><span class="pre">firewall</span> <span class="pre">id</span></code> will be different than the screenshot.</p></li>
 </ul>
 <p><img alt="Existing firewall configuration" src="../_images/lab4-associate-existing-firewall.png" /><br />
 <em>Fig. Existing firewall configuration</em></p>

diff --git a/docs/flightschool/searchindex.js b/docs/flightschool/searchindex.js
diff --git a/flightschool/docs/images/lab1-copilot-topology.png b/flightschool/docs/images/lab1-copilot-topology.png
diff --git a/flightschool/docs/images/lab4-associate-existing-firewall.png b/flightschool/docs/images/lab4-associate-existing-firewall.png
diff --git a/flightschool/docs/lab4.md b/flightschool/docs/lab4.md
@@ -192,7 +192,7 @@ We have already deployed a firewall instance in the lab. In order for Firenet to
 ![Associate existing firewall](images/lab4-associate-existing-firewall-add.png)  
 _Fig. Associate existing firewall_  
 
-* In the pane that opened, add the configuration as shown on the screenshot. Most information shows up when you click on the pull down menu's.
+* In the pane that opened, add the configuration as shown on the screenshot. Most information shows up when you click on the pull down menu's. Note the 6-digit suffix for the `resource group` and `firewall id` will be different than the screenshot.
 
 ![Existing firewall configuration](images/lab4-associate-existing-firewall.png)  
 _Fig. Existing firewall configuration_