Merge pull request #275299 from schaffererin/updateparams1

Updated command parameters with long-form formatting

Author: prmerger-automator[bot]

articles/aks/artifact-streaming.md

@@ -76,7 +76,7 @@ Enablement on ACR is a prerequisite for Artifact Streaming on AKS. For more info
 4. Push or import an image to the registry using the [`az acr import`][az-acr-import] command.
 
     ```azurecli-interactive
-    az acr import --source docker.io/jupyter/all-spark-notebook:latest -t jupyter/all-spark-notebook:latest
+    az acr import --source docker.io/jupyter/all-spark-notebook:latest --repository jupyter/all-spark-notebook:latest
     ```
 
 5. Create a streaming artifact from the image using the [`az acr artifact-streaming create`][az-acr-artifact-streaming-create] command.
@@ -88,7 +88,7 @@ Enablement on ACR is a prerequisite for Artifact Streaming on AKS. For more info
 6. Verify the generated Artifact Streaming using the [`az acr manifest list-referrers`][az-acr-manifest-list-referrers] command.
 
     ```azurecli-interactive
-    az acr manifest list-referrers -n jupyter/all-spark-notebook:latest
+    az acr manifest list-referrers --name jupyter/all-spark-notebook:latest
     ```
 
 ## Enable Artifact Streaming on AKS

articles/aks/cluster-container-registry-integration.md

@@ -37,7 +37,7 @@ The AKS to ACR integration assigns the [**AcrPull** role][acr-pull] to the [Micr
     ```azurecli-interactive
     MYACR=mycontainerregistry
 
-    az acr create -n $MYACR -g myContainerRegistryResourceGroup --sku basic
+    az acr create --name $MYACR --resource-group myContainerRegistryResourceGroup --sku basic
     ```
 
 #### [Azure PowerShell](#tab/azure-powershell)
@@ -61,7 +61,7 @@ The AKS to ACR integration assigns the [**AcrPull** role][acr-pull] to the [Micr
     ```azurecli-interactive
     MYACR=mycontainerregistry
 
-    az aks create -n myAKSCluster -g myResourceGroup --generate-ssh-keys --attach-acr $MYACR
+    az aks create --name myAKSCluster --resource-group myResourceGroup --generate-ssh-keys --attach-acr $MYACR
     ```
 
     This command may take several minutes to complete.
@@ -97,10 +97,10 @@ The AKS to ACR integration assigns the [**AcrPull** role][acr-pull] to the [Micr
 
     ```azurecli-interactive
     # Attach using acr-name
-    az aks update -n myAKSCluster -g myResourceGroup --attach-acr <acr-name>
+    az aks update --name myAKSCluster --resource-group myResourceGroup --attach-acr <acr-name>
 
     # Attach using acr-resource-id
-    az aks update -n myAKSCluster -g myResourceGroup --attach-acr <acr-resource-id>
+    az aks update --name myAKSCluster --resource-group myResourceGroup --attach-acr <acr-resource-id>
     ```
 
     > [!NOTE]
@@ -127,10 +127,10 @@ The AKS to ACR integration assigns the [**AcrPull** role][acr-pull] to the [Micr
 
     ```azurecli-interactive
     # Detach using acr-name
-    az aks update -n myAKSCluster -g myResourceGroup --detach-acr <acr-name>
+    az aks update --name myAKSCluster --resource-group myResourceGroup --detach-acr <acr-name>
 
     # Detach using acr-resource-id
-    az aks update -n myAKSCluster -g myResourceGroup --detach-acr <acr-resource-id>
+    az aks update --name myAKSCluster --resource-group myResourceGroup --detach-acr <acr-resource-id>
     ```
 
 #### [Azure PowerShell](#tab/azure-powershell)
@@ -152,7 +152,7 @@ The AKS to ACR integration assigns the [**AcrPull** role][acr-pull] to the [Micr
 * Import an image from Docker Hub into your ACR using the [`az acr import`][az-acr-import] command.
 
     ```azurecli-interactive
-    az acr import  -n <acr-name> --source docker.io/library/nginx:latest --image nginx:v1
+    az acr import --name <acr-name> --source docker.io/library/nginx:latest --image nginx:v1
     ```
 
 #### [Azure PowerShell](#tab/azure-powershell)
@@ -172,7 +172,7 @@ The AKS to ACR integration assigns the [**AcrPull** role][acr-pull] to the [Micr
 1. Ensure you have the proper AKS credentials using the [`az aks get-credentials`][az-aks-get-credentials] command.
 
     ```azurecli-interactive
-    az aks get-credentials -g myResourceGroup -n myAKSCluster
+    az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
     ```
 
 2. Create a file called **acr-nginx.yaml** using the following sample YAML and replace **acr-name** with the name of your ACR.

articles/aks/edge-zones.md

@@ -254,10 +254,10 @@ az login
 az account set --subscription $SUBSCRIPTION 
 
 # Create the resource group
-az group create -n $RG_NAME -l $LOCATION
+az group create --name $RG_NAME --location $LOCATION
 
 # Deploy the cluster in your designated Edge Zone
-az aks create -g $RG_NAME -n $CLUSTER_NAME --edge-zone $EDGE_ZONE_NAME --location $LOCATION
+az aks create --resource-group $RG_NAME --name $CLUSTER_NAME --edge-zone $EDGE_ZONE_NAME --location $LOCATION
 ```
 
 ### [Azure portal](#tab/azure-portal)

articles/aks/learn/tutorial-kubernetes-workload-identity.md

@@ -79,15 +79,15 @@ To help simplify steps to configure the identities required, the steps below def
 1. Create an AKS cluster using the [az aks create][az-aks-create] command with the `--enable-oidc-issuer` parameter to use the OIDC Issuer.
 
     ```azurecli-interactive
-    az aks create -g "${RESOURCE_GROUP}" -n myAKSCluster --node-count 1 --enable-oidc-issuer --enable-workload-identity --generate-ssh-keys
+    az aks create --resource-group "${RESOURCE_GROUP}" --name myAKSCluster --node-count 1 --enable-oidc-issuer --enable-workload-identity --generate-ssh-keys
     ```
 
     After a few minutes, the command completes and returns JSON-formatted information about the cluster.
 
 2. Get the OIDC Issuer URL and save it to an environmental variable using the following command. Replace the default value for the arguments `-n`, which is the name of the cluster.
 
     ```azurecli-interactive
-    export AKS_OIDC_ISSUER="$(az aks show -n myAKSCluster -g "${RESOURCE_GROUP}" --query "oidcIssuerProfile.issuerUrl" -otsv)"
+    export AKS_OIDC_ISSUER="$(az aks show --name myAKSCluster --resource-group "${RESOURCE_GROUP}" --query "oidcIssuerProfile.issuerUrl" -o tsv)"
     ```
 
     The variable should contain the Issuer URL similar to the following example:
@@ -122,7 +122,7 @@ To help simplify steps to configure the identities required, the steps below def
 3. Add the Key Vault URL to the environment variable `KEYVAULT_URL` using the [az keyvault show][az-keyvault-show] command.
 
     ```bash
-    export KEYVAULT_URL="$(az keyvault show -g "${RESOURCE_GROUP}" -n ${KEYVAULT_NAME} --query properties.vaultUri -o tsv)"
+    export KEYVAULT_URL="$(az keyvault show --resource-group "${RESOURCE_GROUP}" --name ${KEYVAULT_NAME} --query properties.vaultUri -o tsv)"
     ```
 
 ## Create a managed identity and grant permissions to access the secret
@@ -154,7 +154,7 @@ To help simplify steps to configure the identities required, the steps below def
 1. Create a Kubernetes service account and annotate it with the client ID of the managed identity created in the previous step using the [az aks get-credentials][az-aks-get-credentials] command. Replace the default value for the cluster name and the resource group name.
 
     ```azurecli-interactive
-    az aks get-credentials -n myAKSCluster -g "${RESOURCE_GROUP}"
+    az aks get-credentials --name myAKSCluster --resource-group "${RESOURCE_GROUP}"
     ```
 
 2. Copy the following multi-line input into your terminal and run the command to create the service account.

articles/aks/manage-node-pools.md

@@ -58,7 +58,7 @@ In this example, we upgrade the *mynodepool* node pool. Since there are two node
 3. List the status of your node pools using the [`az aks nodepool list`][az-aks-nodepool-list] command.
 
     ```azurecli-interactive
-    az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
+    az aks nodepool list --resource-group myResourceGroup --cluster-name myAKSCluster
     ```
 
      The following example output shows *mynodepool* is in the *Upgrading* state:
@@ -144,7 +144,7 @@ As your application workload demands change, you may need to scale the number of
 2. List the status of your node pools using the [`az aks node pool list`][az-aks-nodepool-list] command.
 
     ```azurecli-interactive
-    az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
+    az aks nodepool list --resource-group myResourceGroup --cluster-name myAKSCluster
     ```
 
      The following example output shows *mynodepool* is in the *Scaling* state with a new count of five nodes:
@@ -326,7 +326,7 @@ In the following example, we create a GPU-based node pool that uses the *Standar
 2. Check the status of the node pool using the [`az aks nodepool list`][az-aks-nodepool-list] command.
 
     ```azurecli-interactive
-    az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
+    az aks nodepool list --resource-group myResourceGroup --cluster-name myAKSCluster
     ```
 
     The following example output shows the *gpunodepool* node pool is *Creating* nodes with the specified *VmSize*:

articles/aks/manage-ssh-node-access.md

@@ -142,7 +142,7 @@ Use the [`az aks create`][az-aks-create] command to create a new cluster, and in
 > After you disable the SSH service, you can't SSH into the cluster to perform administrative tasks or to troubleshoot.
 
 ```azurecli-interactive
-az aks create -g myResourceGroup -n myManagedCluster --ssh-access disabled
+az aks create --resource-group myResourceGroup --name myManagedCluster --ssh-access disabled
 ```
 
 After a few minutes, the command completes and returns JSON-formatted information about the cluster. The following example resembles the output and the results related to disabling SSH:
@@ -158,7 +158,7 @@ After a few minutes, the command completes and returns JSON-formatted informatio
 Use the [`az aks update`][az-aks-update] command to update an existing cluster, and include the `--ssh-access disabled` argument to disable SSH (preview) on all the node pools in the cluster.
 
 ```azurecli-interactive
-az aks update -g myResourceGroup -n myManagedCluster --ssh-access disabled
+az aks update --resource-group myResourceGroup --name myManagedCluster --ssh-access disabled
 ```
 
 After a few minutes, the command completes and returns JSON-formatted information about the cluster. The following example resembles the output and the results related to disabling SSH:
@@ -221,7 +221,7 @@ az aks nodepool upgrade --cluster-name myManagedCluster --name mynodepool --reso
 Use the [`az aks update`][az-aks-update] command to update an existing cluster, and include the `--ssh-access localuser` argument to re-enable SSH (preview) on all the node pools in the cluster.
 
 ```azurecli-interactive
-az aks update -g myResourceGroup -n myManagedCluster --ssh-access localuser
+az aks update --resource-group myResourceGroup --name myManagedCluster --ssh-access localuser
 ```
 
 The following message is returned while the process is performed:

articles/aks/private-clusters.md

@@ -48,15 +48,15 @@ Private cluster is available in public regions, Azure Government, and Microsoft
 Create a resource group using the [`az group create`][az-group-create] command. You can also use an existing resource group for your AKS cluster.
 
 ```azurecli-interactive
-az group create -l eastus -n myResourceGroup
+az group create --location eastus --name myResourceGroup
 ```
 
 ### Default basic networking
 
 Create a private cluster with default basic networking using the [`az aks create`][az-aks-create] command with the `--enable-private-cluster` flag.
 
 ```azurecli-interactive
-az aks create -n <private-cluster-name> -g <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster  
+az aks create --name <private-cluster-name> --resource-group-name <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster  
 ```
 
 ### Advanced networking  
@@ -86,15 +86,15 @@ If you want to configure custom domains that can only be resolved internally, se
 Disable a public FQDN when creating a private AKS cluster using the `--disable-public-fqdn` flag.
 
 ```azurecli-interactive
-az aks create -n <private-cluster-name> -g <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <resourceID> --private-dns-zone <private-dns-zone-mode> --disable-public-fqdn
+az aks create --name <private-cluster-name> --resource-group <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <resourceID> --private-dns-zone <private-dns-zone-mode> --disable-public-fqdn
 ```
 
 ### Disable a public FQDN on an existing cluster
 
 Disable a public FQDN on an existing AKS cluster using the [`az aks update`][az-aks-update] command with the `--disable-public-fqdn` flag.
 
 ```azurecli-interactive
-az aks update -n <private-cluster-name> -g <private-cluster-resource-group> --disable-public-fqdn
+az aks update --name <private-cluster-name> --resource-group <private-cluster-resource-group> --disable-public-fqdn
 ```
 
 ## Configure a private DNS zone
@@ -128,7 +128,7 @@ You can configure private DNS zones using the following parameters:
 Create a private AKS cluster with a private DNS zone using the [`az aks create`][az-aks-create] command with the following flags:
 
 ```azurecli-interactive
-az aks create -n <private-cluster-name> -g <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <resourceID> --private-dns-zone [system|none]
+az aks create --name <private-cluster-name> --resource-group <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <resourceID> --private-dns-zone [system|none]
 ```
 
 ### Create a private AKS cluster with a custom private DNS zone or private DNS subzone
@@ -138,7 +138,7 @@ Create a private AKS cluster with a custom private DNS zone or subzone using the
 ```azurecli-interactive
 # The custom private DNS zone name should be in the following format: "<subzone>.privatelink.<region>.azmk8s.io"
 
-az aks create -n <private-cluster-name> -g <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <resourceID> --private-dns-zone <custom private dns zone or custom private dns subzone resourceID>
+az aks create --name <private-cluster-name> --resource-group <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <resourceID> --private-dns-zone <custom private dns zone or custom private dns subzone resourceID>
 ```
 
 ### Create a private AKS cluster with a custom private DNS zone and custom subdomain
@@ -148,7 +148,7 @@ Create a private AKS cluster with a custom private DNS zone and subdomain using
 ```azurecli-interactive
 # The custom private DNS zone name should be in one of the following formats: "privatelink.<region>.azmk8s.io" or "<subzone>.privatelink.<region>.azmk8s.io"
 
-az aks create -n <private-cluster-name> -g <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <resourceID> --private-dns-zone <custom private dns zone resourceID> --fqdn-subdomain <subdomain>
+az aks create --name <private-cluster-name> --resource-group <private-cluster-resource-group> --load-balancer-sku standard --enable-private-cluster --enable-managed-identity --assign-identity <resourceID> --private-dns-zone <custom private dns zone resourceID> --fqdn-subdomain <subdomain>
 ```
 
 ### Update a private cluster from a private DNS zone to public
@@ -159,7 +159,7 @@ az aks create -n <private-cluster-name> -g <private-cluster-resource-group> --lo
 Update a private cluster from `byo` or `system` to `none` using the [`az aks update`][az-aks-update] command with the following flags:
 
 ```azurecli-interactive
-az aks update -n <private-cluster-name> -g <private-cluster-resource-group> --private-dns-zone none
+az aks update --name <private-cluster-name> --resource-group <private-cluster-resource-group> --private-dns-zone none
 ```
 
 > [!NOTE]

articles/aks/quickstart-event-grid.md

@@ -31,7 +31,7 @@ Create an AKS cluster using the [az aks create][az-aks-create] command. The foll
 
 ```azurecli-interactive
 az group create --name MyResourceGroup --location eastus
-az aks create -g MyResourceGroup -n MyAKS --location eastus  --node-count 1 --generate-ssh-keys
+az aks create --resource-group yResourceGroup --name MyAKS --location eastus  --node-count 1 --generate-ssh-keys
 ```
 
 ### [Azure PowerShell](#tab/azure-powershell)
@@ -52,8 +52,8 @@ New-AzAksCluster -ResourceGroupName MyResourceGroup -Name MyAKS -Location eastus
 Create a namespace and event hub using [az eventhubs namespace create][az-eventhubs-namespace-create] and [az eventhubs eventhub create][az-eventhubs-eventhub-create]. The following example creates a namespace *MyNamespace* and an event hub *MyEventGridHub* in *MyNamespace*, both in the *MyResourceGroup* resource group.
 
 ```azurecli-interactive
-az eventhubs namespace create --location eastus --name MyNamespace -g MyResourceGroup
-az eventhubs eventhub create --name MyEventGridHub --namespace-name MyNamespace -g MyResourceGroup
+az eventhubs namespace create --location eastus --name MyNamespace --resource-group MyResourceGroup
+az eventhubs eventhub create --name MyEventGridHub --namespace-name MyNamespace --resource-group MyResourceGroup
 ```
 
 > [!NOTE]
@@ -62,8 +62,8 @@ az eventhubs eventhub create --name MyEventGridHub --namespace-name MyNamespace
 Subscribe to the AKS events using [az eventgrid event-subscription create][az-eventgrid-event-subscription-create]:
 
 ```azurecli-interactive
-SOURCE_RESOURCE_ID=$(az aks show -g MyResourceGroup -n MyAKS --query id --output tsv)
-ENDPOINT=$(az eventhubs eventhub show -g MyResourceGroup -n MyEventGridHub --namespace-name MyNamespace --query id --output tsv)
+SOURCE_RESOURCE_ID=$(az aks show --resource-group MyResourceGroup --name MyAKS --query id --output tsv)
+ENDPOINT=$(az eventhubs eventhub show --resource-group MyResourceGroup --name MyEventGridHub --namespace-name MyNamespace --query id --output tsv)
 az eventgrid event-subscription create --name MyEventGridSubscription \
 --source-resource-id $SOURCE_RESOURCE_ID \
 --endpoint-type eventhub \

articles/aks/tutorial-kubernetes-paas-services.md

@@ -71,13 +71,13 @@ In previous tutorials, you used a RabbitMQ container to store orders submitted b
 1. Create an Azure Service Bus namespace using the [`az servicebus namespace create`][az-servicebus-namespace-create] command.
 
     ```azurecli-interactive
-    az servicebus namespace create -n $SB_NS -g $RG_NAME -l $LOC_NAME
+    az servicebus namespace create --name $SB_NS --resource-group $RG_NAME --location $LOC_NAME
     ```
 
 2. Create an Azure Service Bus queue using the [`az servicebus queue create`][az-servicebus-queue-create] command.
 
     ```azurecli-interactive
-    az servicebus queue create -n orders -g $RG_NAME --namespace-name $SB_NS -g $RG_NAME
+    az servicebus queue create --name orders --resource-group $RG_NAME --namespace-name $SB_NS
     ```
 
 3. Create an Azure Service Bus authorization rule using the [`az servicebus queue authorization-rule create`][az-servicebus-queue-authorization-rule-create] command.