Merge pull request #190536 from dksimpson/azure-docs-pr-20220126-validation-8

Validation bulk update: Fix code tags for Azure CLI code blocks - batch 8

Author: PRMerger20

articles/container-registry/container-registry-authentication.md

@@ -71,7 +71,7 @@ Output displays the access token, abbreviated here:
 ```
 For registry authentication, we recommend that you store the token credential in a safe location and follow recommended practices to manage [docker login](https://docs.docker.com/engine/reference/commandline/login/) credentials. For example, store the token value in an environment variable:
 
-```bash
+```azurecli
 TOKEN=$(az acr login --name <acrName> --expose-token --output tsv --query accessToken)
 ```
 

articles/container-registry/container-registry-check-health.md

@@ -58,13 +58,15 @@ az acr check-health --ignore-errors
 
 # Check environment and target registry; skip confirmation to pull image
 az acr check-health --name myregistry --ignore-errors --yes
-```      
+```
 
 Sample output:
 
-```console
-$ az acr check-health --name myregistry --ignore-errors --yes
+```azurecli
+az acr check-health --name myregistry --ignore-errors --yes
+```
 
+```output
 Docker daemon status: available
 Docker version: Docker version 18.09.2, build 6247962
 Docker pull of 'mcr.microsoft.com/mcr/hello-world:latest' : OK

articles/container-registry/container-registry-customer-managed-keys.md

@@ -131,7 +131,7 @@ az keyvault set-policy \
 
 Alternatively, use [Azure RBAC for Key Vault](../key-vault/general/rbac-guide.md) to assign permissions to the identity to access the key vault. For example, assign the Key Vault Crypto Service Encryption role to the identity using the [az role assignment create](/cli/azure/role/assignment#az_role_assignment_create) command:
 
-```azurecli 
+```azurecli
 az role assignment create --assignee $identityPrincipalID \
   --role "Key Vault Crypto Service Encryption User" \
   --scope $keyvaultID
@@ -149,7 +149,7 @@ az keyvault key create \
 
 In the command output, take note of the key's ID, `kid`. You use this ID in the next step:
 
-```JSON
+```output
 [...]
   "key": {
     "crv": null,
@@ -315,7 +315,7 @@ You can also use a Resource Manager template to create a registry and enable enc
 
 The following template creates a new container registry and a user-assigned managed identity. Copy the following contents to a new file and save it using a filename such as `CMKtemplate.json`.
 
-```JSON
+```json
 {
   "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
   "contentVersion": "1.0.0.0",
@@ -425,7 +425,7 @@ Follow the steps in the previous sections to create the following resources:
 
 Run the following [az deployment group create][az-deployment-group-create] command to create the registry using the preceding template file. Where indicated, provide a new registry name and managed identity name, as well as the key vault name and key ID you created.
 
-```bash
+```azurecli
 az deployment group create \
   --resource-group <resource-group-name> \
   --template-file CMKtemplate.json \

articles/container-registry/container-registry-delete.md

@@ -115,7 +115,7 @@ After identifying stale manifest digests, you can run the following Bash script
 > [!WARNING]
 > Use the following sample script with caution--deleted image data is UNRECOVERABLE. If you have systems that pull images by manifest digest (as opposed to image name), you should not run these scripts. Deleting the manifest digests will prevent those systems from pulling the images from your registry. Instead of pulling by manifest, consider adopting a *unique tagging* scheme, a [recommended best practice](container-registry-image-tag-version.md). 
 
-```bash
+```azurecli
 #!/bin/bash
 
 # WARNING! This script deletes data!

articles/container-registry/container-registry-helm-repos.md

@@ -140,7 +140,7 @@ Successfully packaged chart and saved it to: /my/path/hello-world-0.1.0.tgz
 Run  `helm registry login` to authenticate with the registry. You may pass [registry credentials](container-registry-authentication.md) appropriate for your scenario, such as service principal credentials, user identity, or a repository-scoped token.
 
 - Authenticate with an Azure Active Directory [service principal with pull and push permissions](container-registry-auth-service-principal.md#create-a-service-principal) (AcrPush role) to the registry.
-  ```bash
+  ```azurecli
   SERVICE_PRINCIPAL_NAME=<acr-helm-sp>
   ACR_REGISTRY_ID=$(az acr show --name $ACR_NAME --query id --output tsv)
   PASSWORD=$(az ad sp create-for-rbac --name $SERVICE_PRINCIPAL_NAME \
@@ -150,12 +150,12 @@ Run  `helm registry login` to authenticate with the registry. You may pass [regi
   USER_NAME=$(az ad sp list --display-name $SERVICE_PRINCIPAL_NAME --query "[].appId" --output tsv)
   ```
 - Authenticate with your [individual Azure AD identity](container-registry-authentication.md?tabs=azure-cli#individual-login-with-azure-ad) to push and pull Helm charts using an AD token.
-  ```bash
+  ```azurecli
   USER_NAME="00000000-0000-0000-0000-000000000000"
   PASSWORD=$(az acr login --name $ACR_NAME --expose-token --output tsv --query accessToken)
   ```
 - Authenticate with a [repository scoped token](container-registry-repository-scoped-permissions.md) (Preview).
-  ```bash
+  ```azurecli
   USER_NAME="helm-token"
   PASSWORD=$(az acr token create -n $USER_NAME \
                     -r $ACR_NAME \

articles/container-registry/container-registry-java-quickstart.md

@@ -134,7 +134,7 @@ Finally, you'll update your project configuration and use the command prompt to
 
 1. Navigate to the complete project directory for your Spring Boot application and run the following command to build the image and push the image to the registry:
 
-   ```bash
+   ```azurecli
    az acr login && mvn compile jib:build
    ```
 

articles/container-registry/container-registry-oras-artifacts.md

@@ -69,7 +69,7 @@ az acr create \
 
 In the command output, note the `zoneRedundancy` property for the registry. When enabled, the registry is zone redundant, and ORAS Artifact enabled:
 
-```JSON
+```output
 {
   [...]
   "zoneRedundancy": "Enabled",
@@ -98,14 +98,14 @@ Run  `oras login` to authenticate with the registry. You may pass [registry cred
 
 - Authenticate with your [individual Azure AD identity](container-registry-authentication.md?tabs=azure-cli#individual-login-with-azure-ad) to use an AD token.
 
-  ```bash
+  ```azurecli
   USER_NAME="00000000-0000-0000-0000-000000000000"
   PASSWORD=$(az acr login --name $ACR_NAME --expose-token --output tsv --query accessToken)
   ```
 
 - Authenticate with a [repository scoped token](container-registry-repository-scoped-permissions.md) (Preview) to use non-AD based tokens.
 
-  ```bash
+  ```azurecli
   USER_NAME="oras-token"
   PASSWORD=$(az acr token create -n $USER_NAME \
                     -r $ACR_NAME \
@@ -116,7 +116,7 @@ Run  `oras login` to authenticate with the registry. You may pass [registry cred
 
 - Authenticate with an Azure Active Directory [service principal with pull and push permissions](container-registry-auth-service-principal.md#create-a-service-principal) (AcrPush role) to the registry.
 
-  ```bash
+  ```azurecli
   SERVICE_PRINCIPAL_NAME="oras-sp"
   ACR_REGISTRY_ID=$(az acr show --name $ACR_NAME --query id --output tsv)
   PASSWORD=$(az ad sp create-for-rbac --name $SERVICE_PRINCIPAL_NAME \
@@ -364,7 +364,7 @@ The signature is untagged, but tracked as a `oras.artifact.manifest` reference t
 
 Support for the ORAS Artifacts specification enables deleting the graph of artifacts associated with the root artifact. Use the [az acr repository delete][az-acr-repository-delete] command to delete the signature, SBoM and the signature of the SBoM.
 
-```bash
+```azurecli
 az acr repository delete \
   -n $ACR_NAME \
   -t ${REPO}:$TAG -y

articles/container-registry/container-registry-private-link.md

@@ -376,7 +376,7 @@ xxxx.westeurope.cloudapp.azure.com. 10	IN A 20.45.122.144
 
 Also verify that you can perform registry operations from the virtual machine in the network. Make an SSH connection to your virtual machine, and run [az acr login][az-acr-login] to login to your registry. Depending on your VM configuration, you might need to prefix the following commands with `sudo`.
 
-```bash
+```azurecli
 az acr login --name $REGISTRY_NAME
 ```
 

articles/container-registry/container-registry-tutorial-private-base-image-update.md

@@ -179,9 +179,11 @@ az acr task list-runs --registry $ACR_NAME --output table
 
 If you completed the previous tutorial (and didn't delete the registry), you should see output similar to the following. Take note of the number of task runs, and the latest RUN ID, so you can compare the output after you update the base image in the next section.
 
-```console
-$ az acr task list-runs --registry $ACR_NAME --output table
+```azurecli
+az acr task list-runs --registry $ACR_NAME --output table
+```
 
+```output
 UN ID    TASK            PLATFORM    STATUS     TRIGGER       STARTED               DURATION
 --------  --------------  ----------  ---------  ------------  --------------------  ----------
 ca12      baseexample2    linux       Succeeded  Manual        2020-11-21T00:00:56Z  00:00:36
@@ -218,9 +220,11 @@ az acr task list-runs --registry $ACR_NAME --output table
 
 Output is similar to the following. The TRIGGER for the last-executed build should be "Image Update", indicating that the task was kicked off by your quick task of the base image.
 
-```console
-$ az acr task list-runs --registry $ACR_NAME --output table
+```azurecli
+az acr task list-runs --registry $ACR_NAME --output table
+```
 
+```output
          PLATFORM    STATUS     TRIGGER       STARTED               DURATION
 --------  --------------  ----------  ---------  ------------  --------------------  ----------
 ca13      baseexample2    linux       Succeeded  Image Update  2020-11-21T00:06:00Z  00:00:43

articles/container-registry/container-registry-vnet.md

@@ -59,7 +59,7 @@ az network vnet list \
 
 Output:
 
-```console
+```output
 [
   {
     "Name": "myDockerVMVNET",
@@ -91,7 +91,7 @@ az network vnet subnet show \
 
 Output:
 
-```
+```output
 /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myDockerVMVNET/subnets/myDockerVMSubnet
 ```
 
@@ -117,7 +117,7 @@ az acr network-rule add \
 
 After waiting a few minutes for the configuration to update, verify that the VM can access the container registry. Make an SSH connection to your VM, and run the [az acr login][az-acr-login] command to login to your registry. 
 
-```bash
+```azurecli
 az acr login --name mycontainerregistry
 ```
 
@@ -131,7 +131,7 @@ Docker successfully pulls the image to the VM.
 
 This example demonstrates that you can access the private container registry through the network access rule. However, the registry can't be accessed from a login host that doesn't have a network access rule configured. If you attempt to login from another host using the `az acr login` command or `docker login` command, output is similar to the following:
 
-```Console
+```output
 Error response from daemon: login attempt to https://xxxxxxx.azurecr.io/v2/ failed with status: 403 Forbidden
 ```