Merge pull request #276485 from tejaswikolli-web/importimage

edits for git issue

Author: prmerger-automator[bot]

articles/container-registry/container-registry-auto-purge.md

@@ -42,7 +42,7 @@ At a minimum, specify the following when you run `acr purge`:
 
 `acr purge` supports several optional parameters. The following two are used in examples in this article:
 
-* `--untagged` - Specifies that all manifests that don't have associated tags (*untagged manifests*) are deleted. This parameter also deletes untagged manifests in addition to tags that are already being deleted.
+* `--untagged` - Specifies that all manifests that don't have associated tags (*untagged manifests*) are deleted. This parameter also deletes untagged manifests in addition to tags that are already being deleted. Remove all tags associated with a manifest to purge it; only then you can purge a tag free manifest using `--untagged`.
 * `--dry-run` - Specifies that no data is deleted, but the output is the same as if the command is run without this flag. This parameter is useful for testing a purge command to make sure it does not inadvertently delete data you intend to preserve.
 * `--keep` - Specifies that the latest x number of to-be-deleted tags are retained. The latest tags are determined by the last modified time of the tag.
 * `--concurrency` - Specifies a number of purge tasks to process concurrently. A default value is used if this parameter is not provided.

articles/container-registry/container-registry-tasks-reference-yaml.md

@@ -202,6 +202,29 @@ steps:
   - build: -t $Registry/hello-world -f hello-world.dockerfile ./subDirectory
 ```
 
+### Dynamic variable passing in ACR Tasks
+
+When working with Azure container registry (ACR) tasks, you may find yourself needing to pass different values to your build process without changing the task definition by using the `--set` flag with the `az acr task run` command. 
+
+#### Example: Setting image tag at runtime
+
+Suppose you have an ACR task defined in a `acr-task.yml` file with a placeholder for the image tag:
+
+```yaml
+steps:
+  - build: -t $Registry/hello-world:{{.Values.tag}}
+```
+
+You can trigger the task and set the `tag` variable to `v2` at runtime using the following Azure CLI command:
+
+```azurecli
+az acr task run --registry myregistry --name mytask --set tag=v2
+```
+
+This command will start the ACR task named `mytask` and build the image using the `v2` tag, overriding the placeholder in the `acr-task.yml` file.
+
+This approach allows for customization in your CI/CD pipelines, enabling you to dynamically adjust parameters based on your current needs without altering the task definitions.
+
 ## push
 
 Push one or more built or retagged images to a container registry. Supports pushing to private registries like Azure Container Registry, or to the public Docker Hub.
@@ -385,6 +408,7 @@ az acr run -f mounts-secrets.yaml --set-secret mysecret=abcdefg123456 https://gi
 <!-- SOURCE: https://github.com/Azure-Samples/acr-tasks/blob/master/mounts-secrets.yaml -->
 [!code-yml[task](~/acr-tasks/mounts-secrets.yaml)]
 
+
 ## Task step properties
 
 Each step type supports several properties appropriate for its type. The following table defines all of the available step properties. Not all step types support all properties. To see which of these properties are available for each step type, see the [cmd](#cmd), [build](#build), and [push](#push) step type reference sections.

articles/container-registry/monitor-service-reference.md

@@ -24,9 +24,9 @@ Resource Provider and Type: [Microsoft.ContainerRegistry/registries](../azure-mo
 |     AgentPoolCPUTime   | Yes |   Seconds   | Total |   CPU time used by [ACR tasks](container-registry-tasks-overview.md) running on dedicated [agent pools](tasks-agent-pools.md)	         | None | 
 |     RunDuration   | Yes |  Milliseconds   |  Total |  Duration of [ACR tasks](container-registry-tasks-overview.md) runs       | None | 
 |     StorageUsed   |  No | Bytes   |   Average | Storage used by the container registry<br/><br/>Sum of storage for unique and shared layers, manifest files, and replica copies in all repositories<sup>1</sup>	         | Geolocation | 
-|     SuccessfulPullCount | Yes  |   Count   | Total | Successful pulls of container images and other artifacts from the registry	           | None | 
-|     SuccessfulPushCount   | Yes |   Count   | Total | Successful pushes of container images and other artifacts to the registry          | None | 
-|     TotalPullCount   |   Yes | Count   |     Total |  Total pulls of container images and other artifacts from the registry	      | None | 
+|     SuccessfulPullCount | Yes  |   Count   | Total | Successful pulls of container images and other artifacts from the registry. Total get requests to registry v2 manifest api with 200 response.	           | None | 
+|     SuccessfulPushCount   | Yes |   Count   | Total | Successful pushes of container images and other artifacts to the registry.         | None | 
+|     TotalPullCount   |   Yes | Count   |     Total |  Total pulls of container images and other artifacts from the registry. Total get requests to registry v2 manifest api.      | None | 
 |     TotalPushCount   | Yes |  Count   |   Total |  Total pushes of container images and other artifacts to the registry	        | None | 
 
 <sup>1</sup>Because of layer sharing, registry storage used may be less than the sum of storage for individual repositories. When you [delete](container-registry-delete.md) a repository or tag, you recover only the storage used by manifest files and the unique layers referenced.