Sync Terraform module documentation

PaloAltoNetworks · Aug 9, 2023 · ca35e19 · ca35e19
1 parent b2257ce
commit ca35e19
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 4 deletions.
diff --git a/...orm/docs/swfw/aws/vmseries/reference-architectures/combined_design_autoscale.md b/...orm/docs/swfw/aws/vmseries/reference-architectures/combined_design_autoscale.md
@@ -61,8 +61,8 @@ The following steps should be followed before deploying the Terraform code prese
 7. Configure interface management profile to enable health checks from GWLB
 8. Configure network interfaces and subinterfaces, zones and virtual router in template
 9. Configure [static routes with path monitoring](https://docs.paloaltonetworks.com/pan-os/10-1/pan-os-networking-admin/static-routes/configure-path-monitoring-for-a-static-route)
-Details
-
+<details><summary>Details</summary>
+<p>
 Using multiple template stacks, one for each AZ complicates autoscaling and the Panorama Licensing plugin configuration. The virtual router (VR) configuration combined with path monitoring outlined below avoids using AZ-specific template stacks and variables.
 
 **Virtual Router Configuration**
@@ -86,13 +86,15 @@ Below there is shown example of VR configuration with static routes and path mon
 | app2_az2 | 10.105.0.0/16 | 10.100.65.1 | 12 | 10.100.65.1 |
 | health_az1 | 10.100.0.0/16 | 10.100.1.1 | 11 | 10.100.1.1 |
 | health_az2 | 10.100.0.0/16 | 10.100.65.1 | 12 | 10.100.65.1 |
+</p>
 
 An example XML configuration snippet (for PANOS 10.2.3) of the described configuration can be found [here](template-asg-path-monitoring.xml), which after importing to Panorama, can be merged using the command:
 
 ```
 load config partial mode merge from-xpath /config/devices/entry/template/entry[@name='asg'] to-xpath /config/devices/entry/template/entry[@name='asg'] from template-asg-path-monitoring.xml
 ```
 
+</details>
 10. Configure VPC peering between VPC with Panorama and VPC with VM-Series in autoscaling group (after deploying that example)
 
 ## Usage

diff --git a/...orm/docs/swfw/aws/vmseries/reference-architectures/isolated_design_autoscale.md b/...orm/docs/swfw/aws/vmseries/reference-architectures/isolated_design_autoscale.md
@@ -57,8 +57,8 @@ The following steps should be followed before deploying the Terraform code prese
 7. Configure interface management profile to enable health checks from GWLB
 8. Configure network interfaces and subinterfaces, zones and virtual router in template
 9. Configure [static routes with path monitoring](https://docs.paloaltonetworks.com/pan-os/10-1/pan-os-networking-admin/static-routes/configure-path-monitoring-for-a-static-route)
-Details
-
+<details><summary>Details</summary>
+<p>
 Using multiple template stacks, one for each AZ complicates autoscaling and the Panorama Licensing plugin configuration. The virtual router (VR) configuration combined with path monitoring outlined below avoids using AZ-specific template stacks and variables.
 
 **Virtual Router Configuration**
@@ -82,13 +82,15 @@ Below there is shown example of VR configuration with static routes and path mon
 | app2_az2 | 10.105.0.0/16 | 10.100.65.1 | 12 | 10.100.65.1 |
 | health_az1 | 10.100.0.0/16 | 10.100.1.1 | 11 | 10.100.1.1 |
 | health_az2 | 10.100.0.0/16 | 10.100.65.1 | 12 | 10.100.65.1 |
+</p>
 
 An example XML configuration snippet (for PANOS 10.2.3) of the described configuration can be found [here](template-asg-path-monitoring.xml), which after importing to Panorama, can be merged using the command:
 
 ```
 load config partial mode merge from-xpath /config/devices/entry/template/entry[@name='asg'] to-xpath /config/devices/entry/template/entry[@name='asg'] from template-asg-path-monitoring.xml
 ```
 
+</details> 
 10. Configure VPC peering between VPC with Panorama and VPC with VM-Series in autoscaling group (after deploying that example)
 
 ## Usage