Skip to content

Commit 75324b3

Browse files
authored
Merge pull request #108694 from dksimpson/DKS-US1669724-4
Fix tags in Azure CLI code blocks - batch 4
2 parents 92177a5 + b38b512 commit 75324b3

8 files changed

+22
-22
lines changed

articles/ansible/ansible-create-vm.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -216,7 +216,7 @@ This section walks you through running the sample Ansible playbook presented in
216216

217217
1. Create a file (to contain your playbook) named `azure_create_complete_vm.yml`, and open it in the VI editor, as follows:
218218

219-
```azurecli-interactive
219+
```bash
220220
vi azure_create_complete_vm.yml
221221
```
222222

articles/ansible/ansible-manage-linux-vm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ In this section, you use Ansible to deallocate (stop) an Azure virtual machine.
2929

3030
1. Create a file named `azure-vm-stop.yml`, and open it in the editor:
3131

32-
```azurecli-interactive
32+
```bash
3333
code azure-vm-stop.yml
3434
```
3535

@@ -82,7 +82,7 @@ In this section, you use Ansible to start a deallocated (stopped) Azure virtual
8282

8383
1. Create a file named `azure-vm-start.yml`, and open it in the editor:
8484

85-
```azurecli-interactive
85+
```bash
8686
code azure-vm-start.yml
8787
```
8888

articles/application-gateway/ingress-controller-autoscale-pods.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ We are going to use following two components:
2424

2525
1. We will first create an Azure AAD service principal and assign it `Monitoring Reader` access over Application Gateway's resource group.
2626

27-
```bash
27+
```azurecli
2828
applicationGatewayGroupName="<application-gateway-group-id>"
2929
applicationGatewayGroupId=$(az group show -g $applicationGatewayGroupName -o tsv --query "id")
3030
az ad sp create-for-rbac -n "azure-k8s-metric-adapter-sp" --role "Monitoring Reader" --scopes applicationGatewayGroupId

articles/application-gateway/ingress-controller-install-existing.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -87,13 +87,13 @@ important. The resource group required in the command below is *not* the one ref
8787
the resource group of the `aks-agentpool` virtual machines. Typically that resource group starts with `MC_` and contains
8888
the name of your AKS. For instance: `MC_resourceGroup_aksABCD_westus`
8989

90-
```bash
90+
```azurecli
9191
az identity create -g <agent-pool-resource-group> -n <identity-name>
9292
```
9393

9494
1. For the role assignment commands below we need to obtain `principalId` for the newly created identity:
9595

96-
```bash
96+
```azurecli
9797
az identity show -g <resourcegroup> -n <identity-name>
9898
```
9999

@@ -102,7 +102,7 @@ look something like this: `/subscriptions/A/resourceGroups/B/providers/Microsoft
102102

103103
Get the list of Application Gateway IDs in your subscription with: `az network application-gateway list --query '[].id'`
104104

105-
```bash
105+
```azurecli
106106
az role assignment create \
107107
--role Contributor \
108108
--assignee <principalId> \
@@ -112,7 +112,7 @@ look something like this: `/subscriptions/A/resourceGroups/B/providers/Microsoft
112112
1. Give the identity `Reader` access to the Application Gateway resource group. The resource group ID would look like:
113113
`/subscriptions/A/resourceGroups/B`. You can get all resource groups with: `az group list --query '[].id'`
114114

115-
```bash
115+
```azurecli
116116
az role assignment create \
117117
--role Reader \
118118
--assignee <principalId> \
@@ -125,7 +125,7 @@ It is also possible to provide AGIC access to ARM via a Kubernetes secret.
125125
1. Create an Active Directory Service Principal and encode with base64. The base64 encoding is required for the JSON
126126
blob to be saved to Kubernetes.
127127

128-
```bash
128+
```azurecli
129129
az ad sp create-for-rbac --subscription <subscription-uuid> --sdk-auth | base64 -w0
130130
```
131131

articles/application-gateway/ingress-controller-install-new.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ installed in an environment with no pre-existing components.
1616

1717
## Required Command Line Tools
1818

19-
We recommend the use of [Azure Cloud Shell](https://shell.azure.com/) for all command line operations below. Launch your shell from shell.azure.com or by clicking the link:
19+
We recommend the use of [Azure Cloud Shell](https://shell.azure.com/) for all command-line operations below. Launch your shell from shell.azure.com or by clicking the link:
2020

2121
[![Embed launch](https://shell.azure.com/images/launchcloudshell.png "Launch Azure Cloud Shell")](https://shell.azure.com)
2222

@@ -25,7 +25,7 @@ Alternatively, launch Cloud Shell from Azure portal using the following icon:
2525
![Portal launch](./media/application-gateway-ingress-controller-install-new/portal-launch-icon.png)
2626

2727
Your [Azure Cloud Shell](https://shell.azure.com/) already has all necessary tools. Should you
28-
choose to use another environment, please ensure the following command line tools are installed:
28+
choose to use another environment, please ensure the following command-line tools are installed:
2929

3030
* `az` - Azure CLI: [installation instructions](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)
3131
* `kubectl` - Kubernetes command-line tool: [installation instructions](https://kubernetes.io/docs/tasks/tools/install-kubectl)
@@ -38,7 +38,7 @@ choose to use another environment, please ensure the following command line tool
3838
Follow the steps below to create an Azure Active Directory (AAD) [service principal object](https://docs.microsoft.com/azure/active-directory/develop/app-objects-and-service-principals#service-principal-object). Please record the `appId`, `password`, and `objectId` values - these will be used in the following steps.
3939

4040
1. Create AD service principal ([Read more about RBAC](https://docs.microsoft.com/azure/role-based-access-control/overview)):
41-
```bash
41+
```azurecli
4242
az ad sp create-for-rbac --skip-assignment -o json > auth.json
4343
appId=$(jq -r ".appId" auth.json)
4444
password=$(jq -r ".password" auth.json)
@@ -47,7 +47,7 @@ Follow the steps below to create an Azure Active Directory (AAD) [service princi
4747
4848
4949
1. Use the `appId` from the previous command's output to get the `objectId` of the new service principal:
50-
```bash
50+
```azurecli
5151
objectId=$(az ad sp show --id $appId --query "objectId" -o tsv)
5252
```
5353
The output of this command is `objectId`, which will be used in the Azure Resource Manager template below
@@ -80,7 +80,7 @@ This step will add the following components to your subscription:
8080
```
8181
8282
1. Deploy the Azure Resource Manager template using `az cli`. This may take up to 5 minutes.
83-
```bash
83+
```azurecli
8484
resourceGroupName="MyResourceGroup"
8585
location="westus2"
8686
deploymentName="ingress-appgw"
@@ -97,22 +97,22 @@ This step will add the following components to your subscription:
9797
```
9898
9999
1. Once the deployment finished, download the deployment output into a file named `deployment-outputs.json`.
100-
```bash
100+
```azurecli
101101
az group deployment show -g $resourceGroupName -n $deploymentName --query "properties.outputs" -o json > deployment-outputs.json
102102
```
103103
104104
## Set up Application Gateway Ingress Controller
105105
106-
With the instructions in the previous section we created and configured a new AKS cluster and
106+
With the instructions in the previous section, we created and configured a new AKS cluster and
107107
an Application Gateway. We are now ready to deploy a sample app and an ingress controller to our new
108108
Kubernetes infrastructure.
109109
110110
### Setup Kubernetes Credentials
111-
For the following steps we need setup [kubectl](https://kubectl.docs.kubernetes.io/) command,
111+
For the following steps, we need setup [kubectl](https://kubectl.docs.kubernetes.io/) command,
112112
which we will use to connect to our new Kubernetes cluster. [Cloud Shell](https://shell.azure.com/) has `kubectl` already installed. We will use `az` CLI to obtain credentials for Kubernetes.
113113
114114
Get credentials for your newly deployed AKS ([read more](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough#connect-to-the-cluster)):
115-
```bash
115+
```azurecli
116116
# use the deployment-outputs.json created after deployment to get the cluster name and resource group name
117117
aksClusterName=$(jq -r ".aksClusterName.value" deployment-outputs.json)
118118
resourceGroupName=$(jq -r ".resourceGroupName.value" deployment-outputs.json)
@@ -268,7 +268,7 @@ Kubernetes. We will leverage it to install the `application-gateway-kubernetes-i
268268
> The `identityResourceID` and `identityClientID` are values that were created
269269
during the [Create an Identity](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/072626cb4e37f7b7a1b0c4578c38d1eadc3e8701/docs/setup/install-new.md#create-an-identity)
270270
steps, and could be obtained again using the following command:
271-
> ```bash
271+
> ```azurecli
272272
> az identity show -g <resource-group> -n <identity-name>
273273
> ```
274274
> `<resource-group>` in the command above is the resource group of your Application Gateway. `<identity-name>` is the name of the created identity. All identities for a given subscription can be listed using: `az identity list`

articles/application-gateway/quick-create-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,7 @@ It can take up to 30 minutes for Azure to create the application gateway. After
167167

168168
Although Azure doesn't require an NGINX web server to create the application gateway, you installed it in this quickstart to verify whether Azure successfully created the application gateway. To get the public IP address of the new application gateway, use `az network public-ip show`.
169169

170-
```azurepowershell-interactive
170+
```azurecli-interactive
171171
az network public-ip show \
172172
--resource-group myResourceGroupAG \
173173
--name myAGPublicIPAddress \

articles/application-gateway/tutorial-create-vmss-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ az vmss extension set \
123123

124124
To get the public IP address of the application gateway, you can use [az network public-ip show](/cli/azure/network/public-ip). Copy the public IP address, and then paste it into the address bar of your browser.
125125

126-
```azurepowershell-interactive
126+
```azurecli-interactive
127127
az network public-ip show \
128128
--resource-group myResourceGroupAG \
129129
--name myAGPublicIPAddress \

articles/application-gateway/tutorial-url-redirect-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -282,7 +282,7 @@ done
282282

283283
To get the public IP address of the application gateway, use [az network public-ip show](/cli/azure/network/public-ip#az-network-public-ip-show). Copy the public IP address, and then paste it into the address bar of your browser. Such as, `http://40.121.222.19`, `http://40.121.222.19:8080/images/test.htm`, `http://40.121.222.19:8080/video/test.htm`, or `http://40.121.222.19:8081/images/test.htm`.
284284

285-
```azurepowershell-interactive
285+
```azurecli-interactive
286286
az network public-ip show \
287287
--resource-group myResourceGroupAG \
288288
--name myAGPublicIPAddress \

0 commit comments

Comments
 (0)