Merge pull request #264371 from tejaswikolli-web/artifactpush

manage-artifacts

Author: JamesJBarnett

.openpublishing.redirection.container-registry.json

@@ -1,10 +1,22 @@
 {
     "redirections": [
+        
+        {
+            "source_path_from_root": "/articles/container-registry/container-registry-oci-artifacts.md",
+            "redirect_url": "/azure/container-registry/container-registry-manage-artifact",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/container-registry/container-registry-oras-artifacts.md",
+            "redirect_url": "/azure/container-registry/container-registry-manage-artifact",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/container-registry/tutorial-enable-registry-cache-auth.md",
             "redirect_url": "/azure/container-registry/container-registry-artifact-cache",
             "redirect_document_id": false
         },
+        
         {
             "source_path_from_root": "/articles/container-registry/tutorial-enable-registry-cache-auth-cli.md",
             "redirect_url": "/azure/container-registry/container-registry-artifact-cache",

articles/container-registry/TOC.yml

@@ -98,12 +98,10 @@
       items:
       - name: Push and pull an image
         href: container-registry-get-started-docker-cli.md
-      - name: Push and pull an OCI artifact
-        href: container-registry-oci-artifacts.md
       - name: Push and pull a Helm chart
         href: container-registry-helm-repos.md
-      - name: Push and pull supply chain artifacts (preview)
-        href: container-registry-oras-artifacts.md
+      - name: Manage artifacts with ORAS
+        href: container-registry-manage-artifact.md
       - name: View repositories
         href: container-registry-repositories.md
       - name: Import container images

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

@@ -49,7 +49,7 @@ az acr login --name <acrName>
 When you log in with `az acr login`, the CLI uses the token created when you executed `az login` to seamlessly authenticate your session with your registry. To complete the authentication flow, the Docker CLI and Docker daemon must be installed and running in your environment. `az acr login` uses the Docker client to set a Microsoft Entra token in the `docker.config` file. Once you've logged in this way, your credentials are cached, and subsequent `docker` commands in your session do not require a username or password.
 
 > [!TIP]
-> Also use `az acr login` to authenticate an individual identity when you want to push or pull artifacts other than Docker images to your registry, such as [OCI artifacts](container-registry-oci-artifacts.md).
+> Also use `az acr login` to authenticate an individual identity when you want to push or pull artifacts other than Docker images to your registry, such as [OCI artifacts](container-registry-manage-artifact.md).
 
 For registry access, the token used by `az acr login` is valid for **3 hours**, so we recommend that you always log in to the registry before running a `docker` command. If your token expires, you can refresh it by using the `az acr login` command again to reauthenticate.
 
@@ -104,7 +104,7 @@ Connect-AzContainerRegistry -Name <acrName>
 When you log in with `Connect-AzContainerRegistry`, PowerShell uses the token created when you executed `Connect-AzAccount` to seamlessly authenticate your session with your registry. To complete the authentication flow, the Docker CLI and Docker daemon must be installed and running in your environment. `Connect-AzContainerRegistry` uses the Docker client to set a Microsoft Entra token in the `docker.config` file. Once you've logged in this way, your credentials are cached, and subsequent `docker` commands in your session do not require a username or password.
 
 > [!TIP]
-> Also use `Connect-AzContainerRegistry` to authenticate an individual identity when you want to push or pull artifacts other than Docker images to your registry, such as [OCI artifacts](container-registry-oci-artifacts.md).
+> Also use `Connect-AzContainerRegistry` to authenticate an individual identity when you want to push or pull artifacts other than Docker images to your registry, such as [OCI artifacts](container-registry-manage-artifact.md).
 
 For registry access, the token used by `Connect-AzContainerRegistry` is valid for **3 hours**, so we recommend that you always log in to the registry before running a `docker` command. If your token expires, you can refresh it by using the `Connect-AzContainerRegistry` command again to reauthenticate.
 

articles/container-registry/container-registry-image-formats.md

@@ -28,7 +28,7 @@ Azure Container Registry supports images that meet the [Open Container Initiativ
 
 Azure Container Registry supports the [OCI Distribution Specification](https://github.com/opencontainers/distribution-spec), a vendor-neutral, cloud-agnostic spec to store, share, secure, and deploy container images and other content types (artifacts). The specification allows a registry to store a wide range of artifacts in addition to container images. You use tooling appropriate to the artifact to push and pull artifacts. For examples, see:
 
-* [Push and pull an OCI artifact using an Azure container registry](container-registry-oci-artifacts.md)
+* [Push and pull an OCI artifact using an Azure container registry](container-registry-manage-artifact.md)
 * [Push and pull Helm charts to an Azure container registry](container-registry-helm-repos.md)
 
 To learn more about OCI artifacts, see the [OCI Registry as Storage (ORAS)](https://github.com/deislabs/oras) repo and the [OCI Artifacts](https://github.com/opencontainers/artifacts) repo on GitHub.