feat: update bash to shell for code blocks (#1104)

Author: JTorreG

content/nginxaas-azure/client-tools/cli.md

@@ -20,14 +20,14 @@ F5 NGINXaaS for Azure (NGINXaaS) deployments can be managed using the [Azure CLI
 
 In order to install and manage your NGINXaaaS deployments using the Azure CLI, you will need to install the `nginx` extension:
 
-```bash
+```shell
 az extension add --name nginx --allow-preview true
 ```
 
 ## Update NGINXaaS extension
 
 Ensure you are running the latest version of the `nginx` CLI extension to take advantage of the latest capabilities available on your NGINXaaS deployments:
 
-```bash
+```shell
 az extension update --name nginx --allow-preview true
 ```

content/nginxaas-azure/disaster-recovery.md

@@ -45,7 +45,7 @@ This guide describes how to configure disaster recovery (DR) for F5 NGINXaaS for
 To get started, please review the [Terraform prerequisites]({{< ref "/nginxaas-azure/getting-started/create-deployment/deploy-terraform.md#prerequisites" >}}) for NGINXaaS for Azure.
 The following steps outline Terraform resources required to set up the disaster recovery topology; these resources can be placed in a `main.tf` file, variables used by these resources can go into `variables.tf`, and outputs you need to collect can be defined in `outputs.tf`. The directory structure looks as follows:
 
-```bash
+```shell
 $ tree
 .
 |-- main.tf
@@ -55,7 +55,7 @@ $ tree
 
 To execute the Terraform code, `cd` into the directory with these files and run:
 
-```bash
+```shell
 terraform init
 terraform plan
 terraform apply --auto-approve

content/nginxaas-azure/getting-started/create-deployment/deploy-azure-cli.md

@@ -19,7 +19,7 @@ The Azure CLI has an extension to be used for management of F5 NGINXaaS for Azur
 
 To create an NGINXaaS for Azure resource use the `az nginx deployment create` command:
 
-```bash
+```shell
 az nginx deployment create --deployment-name
                            --resource-group
                            [--auto-upgrade-profile]
@@ -39,7 +39,7 @@ az nginx deployment create --deployment-name
 
 - Create a deployment with public IP:
 
-   ```bash
+   ```shell
    az nginx deployment create --name myDeployment --resource-group \
       myResourceGroup --location eastus2 --sku name="standardv2_Monthly" \
       --network-profile front-end-ip-configuration="{public-ip-addresses:[{id:/subscriptions/mySubscriptionID/resourceGroups/myResourceGroup/providers/Microsoft.Network/publicIPAddresses/myPublicIP}]}" \
@@ -48,15 +48,15 @@ az nginx deployment create --deployment-name
 
 - Create a deployment with private IP:
 
-   ```bash
+   ```shell
    az nginx deployment create --name myDeployment --resource-group \
       myResourceGroup --location eastus2 --sku \
       name="standardv2_Monthly" --network-profile \
       front-end-ip-configuration="{private-ip-addresses:[{private-ip-allocation-method:Static,subnet-id:/subscriptions/mySubscription/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myVNet/subnets/mySubnet,private-ip-address:10.0.0.2}]}" \
       network-interface-configuration="{subnet-id:/subscriptions/mySubscriptionID/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myVNet/subnets/mySubnet}"
    ```
 
-   ```bash
+   ```shell
    az nginx deployment create --name myDeployment --resource-group \
       myResourceGroup --location eastus2 --sku \
       name="standardv2_Monthly" --network-profile \
@@ -66,7 +66,7 @@ az nginx deployment create --deployment-name
 
 - Create a dual-stack (IPv4 + IPv6) NGINXaaS deployment with public IPs:
 
-   ```bash
+   ```shell
    az nginx deployment create --name myDeployment --resource-group \
       myResourceGroup --location eastus2 --sku name="standardv2_Monthly" \
       --network-profile front-end-ip-configuration="{public-ip-addresses:[{id:/subscriptions/mySubscription/resourceGroups/myResourceGroup/providers/Microsoft.Network/publicIPAddresses/pubIPv4},{id:/subscriptions/mySubscription/resourceGroups/myResourceGroup/providers/Microsoft.Network/publicIPAddresses/pubIPv6}]}" \
@@ -75,7 +75,7 @@ az nginx deployment create --deployment-name
 
 - Create a dual-stack (IPv4 + IPv6) NGINXaaS deployment with private IPs:
 
-   ```bash
+   ```shell
    az nginx deployment create --name myDeployment --resource-group \
       myResourceGroup --location eastus2 --sku \
       name="standardv2_Monthly" --network-profile \
@@ -85,7 +85,7 @@ az nginx deployment create --deployment-name
 
 - Create a deployment with managed identity, storage account and scaling:
 
-   ```bash
+   ```shell
    az nginx deployment create --deployment-name myDeployment --resource-group \
       myResourceGroup --location eastus2 --sku name=standardv2_Monthly \
       --network-profile \
@@ -102,7 +102,7 @@ See the [Azure CLI Deployment Create Documentation](https://learn.microsoft.com/
 
 To update an NGINXaaS for Azure resource use the `az nginx deployment update` command:
 
-```bash
+```shell
 az nginx deployment update [--add]
                            [--auto-upgrade-profile]
                            [--deployment-name]
@@ -128,15 +128,15 @@ az nginx deployment update [--add]
 
 - Update tags and enable diagnostics support for a deployment:
 
-   ```bash
+   ```shell
    az nginx deployment update --name myDeployment --resource-group \
    myResourceGroup --location eastus2 --tags tag1="value1" \
    tag2="value2" --enable-diagnostics
    ```
 
 Update an NGINXaaS deployment to a dual-stack (IPv4 + IPv6) network configuration with public IPs:
 
-   ```bash
+   ```shell
    az nginx deployment update --name myDeployment --resource-group myResourceGroup \
       --network-profile front-end-ip-configuration="{public-ip-addresses:[{id:/subscriptions/mySubscriptionID/resourceGroups/myResourceGroup/providers/Microsoft.Network/publicIPAddresses/pubIPv4},{id:/subscriptions/mySubscriptionID/resourceGroups/myResourceGroup/providers/Microsoft.Network/publicIPAddresses/pubIPv6}]}" \
       network-interface-configuration="{subnet-id:/subscriptions/mySubscriptionID/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myVNet/subnets/mySubnet}"
@@ -149,7 +149,7 @@ See the [Azure CLI Deployment Update Documentation](https://learn.microsoft.com/
 
 Use the `az nginx deployment delete` command to delete an NGINXaaS for Azure resource:
 
-```bash
+```shell
 az nginx deployment delete [--name]
                            [--ids]
                            [--no-wait {0, 1, f, false, n, no, t, true, y, yes}]
@@ -162,7 +162,7 @@ az nginx deployment delete [--name]
 
 - Delete a deployment:
 
-   ```bash
+   ```shell
    az nginx deployment delete --name myDeployment \
       --resource-group myResourceGroup
    ```

content/nginxaas-azure/getting-started/create-deployment/deploy-terraform.md

@@ -21,7 +21,7 @@ You can find examples of Terraform configurations in the [NGINXaaS for Azure Sni
 
 To create a deployment, use the following Terraform commands:
 
-   ```bash
+   ```shell
    terraform init
    terraform plan
    terraform apply --auto-approve
@@ -31,7 +31,7 @@ To create a deployment, use the following Terraform commands:
 
 Once the deployment is no longer needed, run the following to clean up the deployment and related resources:
 
-   ```bash
+   ```shell
    terraform destroy --auto-approve
    ```
 

content/nginxaas-azure/getting-started/migrate-from-standard.md

@@ -47,7 +47,7 @@ terraform {
 
 Run the below command to update your NGINXaaS deployment.
 
-```bash
+```shell
    az nginx deployment update --name myDeployment --resource-group \
    myResourceGroup --sku name="standardv2_Monthly_gmz7xq9ge3py"
 ```

content/nginxaas-azure/getting-started/nginx-configuration/nginx-configuration-azure-cli.md

@@ -23,7 +23,7 @@ F5 NGINXaaS for Azure (NGINXaaS) configurations can be managed using the Azure C
 
 To create a new NGINX configuration, use the `az nginx deployment configuration create` command:
 
-```bash
+```shell
 az nginx deployment configuration create --configuration-name
                                          --deployment-name
                                          --resource-group
@@ -39,7 +39,7 @@ az nginx deployment configuration create --configuration-name
 
 You can use the `analyze` command to validate your configuration before submitting it to the deployment:
 
-```bash
+```shell
 az nginx deployment configuration analyze --deployment-name $DEPLOYMENT_NAME \
    --resource-group $RESOURCE_GROUP --root-file /etc/nginx/nginx.conf \
    --name default --files "$FILES_CONTENT"
@@ -49,7 +49,7 @@ az nginx deployment configuration analyze --deployment-name $DEPLOYMENT_NAME \
 
 - Create a single file configuration:
 
-   ```bash
+   ```shell
    az nginx deployment configuration create --name default \
       --deployment-name myDeployment --resource-group myResourceGroup \
       --root-file /etc/nginx/nginx.conf \
@@ -70,7 +70,7 @@ az nginx deployment configuration analyze --deployment-name $DEPLOYMENT_NAME \
 
 - Create a multiple file configuration:
 
-   ```bash
+   ```shell
    az nginx deployment configuration create --name default \
       --deployment-name myDeployment --resource-group myResourceGroup \
       --root-file /etc/nginx/nginx.conf \
@@ -92,7 +92,7 @@ az nginx deployment configuration analyze --deployment-name $DEPLOYMENT_NAME \
 
 - Upload package with config files:
 
-   ```bash
+   ```shell
    $ tar -czf nginx.tar.gz nginx
    $ tar -tzf nginx.tar.gz
    nginx/
@@ -106,7 +106,7 @@ az nginx deployment configuration analyze --deployment-name $DEPLOYMENT_NAME \
 
    Where `nginx` is a directory with the following structure:
 
-   ```bash
+   ```shell
    $ tree nginx
    nginx
    ├── nginx.conf
@@ -120,7 +120,7 @@ az nginx deployment configuration analyze --deployment-name $DEPLOYMENT_NAME \
 
    Encode your tar.gz file and create your NGINXaaS configuration
 
-   ```bash
+   ```shell
    TAR_DATA=$(base64 -i nginx.tar.gz)
    az nginx deployment configuration create --deployment-name myDeployment \
       --resource-group myResourceGroup --root-file nginx.conf --name default \
@@ -129,7 +129,7 @@ az nginx deployment configuration analyze --deployment-name $DEPLOYMENT_NAME \
 
 - Multiple file configuration with protected files:
 
-   ```bash
+   ```shell
    az nginx deployment configuration create --name default \
       --deployment-name 0102242023test --resource-group azclitest-geo \
       --root-file /etc/nginx/nginx.conf \
@@ -173,7 +173,7 @@ Update a configuration for a deployment using a gzipped archive.
 
 Use the `az nginx deployment configuration update` command to update an existing NGINX configuration:
 
-```bash
+```shell
 az nginx deployment configuration update [--add]
                                          [--configuration-name]
                                          [--deployment-name]
@@ -193,7 +193,7 @@ az nginx deployment configuration update [--add]
 
 - Update content of the first file in a configuration:
 
-   ```bash
+   ```shell
    az nginx deployment configuration update --name default \
       --deployment-name myDeployment --resource-group myResourceGroup \
       --files [0].content="aHR0cCB7CiAgICB1cHN0cmVhbSBhcHAgewogICAgICAgIHpvbmUg \

content/nginxaas-azure/getting-started/nginx-configuration/nginx-configuration-portal.md

@@ -69,7 +69,7 @@ The editing experience consists of a single view for both editing and validation
 
 Given the example gzipped archive,
 
-```bash
+```shell
 $ tar -czf nginx.tar.gz nginx
 $ tar -tzf nginx.tar.gz
 nginx/
@@ -83,7 +83,7 @@ nginx/servers/server2.conf
 
 where `nginx` is a directory with the following structure,
 
-```bash
+```shell
 $ tree nginx
 nginx
 ├── nginx.conf

content/nginxaas-azure/getting-started/nginx-configuration/nginx-configurations-terraform.md

@@ -21,7 +21,7 @@ You can find examples of Terraform configurations in the [NGINXaaS for Azure Sni
 
 To create a deployment and add a configuration, run the following commands:
 
-   ```bash
+   ```shell
    terraform init
    terraform plan
    terraform apply --auto-approve
@@ -31,7 +31,7 @@ To create a deployment and add a configuration, run the following commands:
 
 NGINX configuration files are uploaded and returned as base64 encoded data. We recommend using git or other version control systems to view human-readable differences between configuration files during `terraform plan`. Alternatively, you can decode the file contents to view the whole file. For example,
 
-```bash
+```shell
 $ terraform plan
 ...
 - config_file {
@@ -60,7 +60,7 @@ http {
 
 Once the deployment is no longer needed, run the following to clean up the deployment and related resources:
 
-   ```bash
+   ```shell
    terraform destroy --auto-approve
    ```