[BUG] [ACR] Unable to create OCI manifest in Azure Container Registry

[sajayantony]

Describe the bug
The SDK should enable the client to create an OCIManifest.

Expected behavior
CreateAsync on an OCIManifest succeeds.

Actual behavior (include Exception or Stack Trace)
Exception thrown with error code = "MANIFEST_INVALID"

To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

using Microsoft.Azure.ContainerRegistry;
using Microsoft.Azure.ContainerRegistry.Models;
using Microsoft.Rest.Azure;
using System;
using System.Threading.Tasks;

namespace manifest_test
{
    class Program
    {
        static async Task Main(string[] args)
        {
            var login = "myregistry.azurecr.io";
            var username = "";
            var password = "";


            var client = new AzureContainerRegistryClient(
                new ContainerRegistryCredentials(
                    ContainerRegistryCredentials.LoginMode.Basic,
                    loginUrl: login,
                    username: username,
                    password: password));

            string OciManifestMediaType = "application/vnd.oci.image.manifest.v1+json";
            string V2ManifestMediaType = "application/vnd.docker.distribution.manifest.v2+json";

            var repo = "hello-world";
            var tag = "latest";
            var resp = await client.Manifests.GetAsync("hello-world", "latest", V2ManifestMediaType);
            client = new AzureContainerRegistryClient(
                           new ContainerRegistryCredentials(
                               ContainerRegistryCredentials.LoginMode.Basic,
                               loginUrl: login,
                               username: username,
                               password: password));

            V2Manifest v2Manifest = (V2Manifest)resp;
            OCIManifest manifest = new OCIManifest();
            manifest.Config = v2Manifest.Config;
            manifest.Config.MediaType = "application/vnd.oci.image.config.v1+json";
            manifest.Layers = v2Manifest.Layers;
            manifest.SchemaVersion = 2;

            // MediaType should be OciManifestMediaType
            await client.Manifests.CreateAsync(repo, "test-put-oci", manifest);

            //Throws exception with detail 
            /* 
             * 		Content	"{\"errors\":[{\"code\":\"MANIFEST_INVALID\",\"message\":\"manifest invalid\",\"detail\":{}}]}\n"	string
            */
        }
    }
}

Environment:

Project 'acr' has the following package references
   [net5.0]:
   Top-level Package                        Requested             Resolved
   > Azure.Identity                         1.2.3                 1.2.3
   > Microsoft.Azure.ContainerRegistry      0.10.0-preview        0.10.0-preview
   > Microsoft.Extensions.Hosting           3.1.9                 3.1.9
   > Newtonsoft.Json                        12.0.3                12.0.3
   > System.CommandLine                     2.0.0-beta1.20371.2   2.0.0-beta1.20371.2
   > System.CommandLine.Hosting             0.3.0-alpha.20371.2   0.3.0-alpha.20371.2
   > System.Text.Json                       4.7.1                 4.7.1

[adewaleo]

Hmm, I don't remember concretely. but I think I also ran into this issue.

I think this might be the root cause
swagger hardcodes docker manifest mediatype
generated sdk overrides this mediatype

[yugangw-msft]

fixed