Merge pull request #275321 from schaffererin/updateparams7

Updated command parameters with long-form formatting

Author: prmerger-automator[bot]

articles/aks/node-upgrade-github-actions.md

@@ -151,13 +151,13 @@ This process is better than updating Linux-based kernels manually because Linux
           - name: Upgrade node images
             uses: Azure/[email protected]
             with:
-              inlineScript: az aks upgrade -g {resourceGroupName} -n {aksClusterName} --node-image-only --yes
+              inlineScript: az aks upgrade --resource-group <resourceGroupName> --name <aksClusterName> --node-image-only --yes
     ```
 
     > [!TIP]
-    > You can decouple the `-g` and `-n` parameters from the command by creating new repository secrets like you did for `AZURE_CREDENTIALS`.
+    > You can decouple the `--resource-group` and `--name` parameters from the command by creating new repository secrets like you did for `AZURE_CREDENTIALS`.
     >
-    > If you create secrets for these parameters, you need to replace the `{resourceGroupName}` and `{aksClusterName}` placeholders with their secret counterparts. For example, `${{secrets.RESOURCE_GROUP_NAME}}` and `${{secrets.AKS_CLUSTER_NAME}}`
+    > If you create secrets for these parameters, you need to replace the `<resourceGroupName>` and `<aksClusterName>` placeholders with their secret counterparts. For example, `${{secrets.RESOURCE_GROUP_NAME}}` and `${{secrets.AKS_CLUSTER_NAME}}`
 
 6. Rename the YAML to `upgrade-node-images.yml`.
 7. Select **Commit changes...**, add a commit message, and then select **Commit changes**.
@@ -170,7 +170,7 @@ You can run the workflow manually in addition to the scheduled run by adding a n
 > If you want to upgrade a single node pool instead of all node pools on the cluster, add the `--name` parameter to the `az aks nodepool upgrade` command to specify the node pool name. For example:
 >
 > ```azurecli-interactive
-> az aks nodepool upgrade -g {resourceGroupName} --cluster-name {aksClusterName} --name {{nodePoolName}} --node-image-only
+> az aks nodepool upgrade --resource-group <resourceGroupName> --cluster-name <aksClusterName> --name <nodePoolName> --node-image-only
 > ```
 
 * Add the `workflow_dispatch` trigger under the `on` key:

articles/aks/rdp.md

@@ -26,7 +26,7 @@ This article assumes that you have an existing AKS cluster with a Windows Server
 If you need to reset the password, use `az aks update` to change the password.
 
 ```azurecli-interactive
-az aks update -g myResourceGroup -n myAKSCluster --windows-admin-password $WINDOWS_ADMIN_PASSWORD
+az aks update --resource-group myResourceGroup --name myAKSCluster --windows-admin-password $WINDOWS_ADMIN_PASSWORD
 ```
 
 If you need to reset the username and password, see [Reset Remote Desktop Services or its administrator password in a Windows VM
@@ -68,10 +68,10 @@ You need to get the subnet ID used by your Windows Server node pool and query fo
 * The subnet ID
 
 ```azurecli-interactive
-CLUSTER_RG=$(az aks show -g myResourceGroup -n myAKSCluster --query nodeResourceGroup -o tsv)
-VNET_NAME=$(az network vnet list -g $CLUSTER_RG --query [0].name -o tsv)
-SUBNET_NAME=$(az network vnet subnet list -g $CLUSTER_RG --vnet-name $VNET_NAME --query [0].name -o tsv)
-SUBNET_ID=$(az network vnet subnet show -g $CLUSTER_RG --vnet-name $VNET_NAME --name $SUBNET_NAME --query id -o tsv)
+CLUSTER_RG=$(az aks show --resource-group myResourceGroup --name myAKSCluster --query nodeResourceGroup -o tsv)
+VNET_NAME=$(az network vnet list --resource-group $CLUSTER_RG --query [0].name -o tsv)
+SUBNET_NAME=$(az network vnet subnet list --resource-group $CLUSTER_RG --vnet-name $VNET_NAME --query [0].name -o tsv)
+SUBNET_ID=$(az network vnet subnet show --resource-group $CLUSTER_RG --vnet-name $VNET_NAME --name $SUBNET_NAME --query id -o tsv)
 ```
 
 Now that you've the SUBNET_ID, run the following command in the same Azure Cloud Shell window to create the VM:
@@ -170,8 +170,8 @@ AKS node pool subnets are protected with NSGs (Network Security Groups) by defau
 First, get the resource group and name of the NSG to add the rule to:
 
 ```azurecli-interactive
-CLUSTER_RG=$(az aks show -g myResourceGroup -n myAKSCluster --query nodeResourceGroup -o tsv)
-NSG_NAME=$(az network nsg list -g $CLUSTER_RG --query [].name -o tsv)
+CLUSTER_RG=$(az aks show --resource-group myResourceGroup --name myAKSCluster --query nodeResourceGroup -o tsv)
+NSG_NAME=$(az network nsg list --resource-group $CLUSTER_RG --query [].name -o tsv)
 ```
 
 Then, create the NSG rule:
@@ -305,8 +305,8 @@ az network public-ip delete \
 Delete the NSG rule:
 
 ```azurecli-interactive
-CLUSTER_RG=$(az aks show -g myResourceGroup -n myAKSCluster --query nodeResourceGroup -o tsv)
-NSG_NAME=$(az network nsg list -g $CLUSTER_RG --query [].name -o tsv)
+CLUSTER_RG=$(az aks show --resource-group myResourceGroup --name myAKSCluster --query nodeResourceGroup -o tsv)
+NSG_NAME=$(az network nsg list --resource-group $CLUSTER_RG --query [].name -o tsv)
 az network nsg rule delete \
  --resource-group $CLUSTER_RG \
  --nsg-name $NSG_NAME \
@@ -362,7 +362,7 @@ Go to the node resource group of the AKS cluster. Run the command below in the A
 #### [Azure CLI](#tab/azure-cli)
 
 ```azurecli-interactive
-az aks show -n myAKSCluster -g myResourceGroup --query 'nodeResourceGroup' -o tsv
+az aks show --name myAKSCluster --resource-group myResourceGroup --query 'nodeResourceGroup' -o tsv
 ```
 
 #### [Azure PowerShell](#tab/azure-powershell)

articles/postgresql/flexible-server/tutorial-django-aks-database.md

@@ -213,7 +213,7 @@ Deploy your image to [Docker hub](https://docs.docker.com/get-started/part3/#cre
 > If you are using Azure container registry (ACR), then run the `az aks update` command to attach ACR account with the AKS cluster.
 >
 > ```azurecli-interactive
-> az aks update -n djangoappcluster -g django-project --attach-acr <your-acr-name>
+> az aks update --name djangoappcluster --resource-group django-project --attach-acr <your-acr-name>
 > ```
 
 ## Create Kubernetes manifest file