Add OCI Conformance validation with ORAS

[SteveLasker]

Add several steps to validate if a registry supports OCI Artifact types using oras push|pull

Signed-off-by: Steve Lasker stevenlasker@hotmail.com

[sajayantony]

Distribution's auth model is bearer token and not basic. You could call out -

Assuming the registry supports username and password authentication for login.

[sajayantony]

would you like to use recommended mime types like text/plain?
https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types

[jdolitsky]

I think this is better to be codified. Perhaps a bash script that runs these commands, taking REGISTRY_URL REGISTRY_NAMESPACE REGISTRY_USERNAME REGISTRY_PASSWORD as env vars

[jdolitsky]

Can also wrap this in robot framework to get some better output. See this example in Helm: https://github.com/helm/acceptance-testing/blob/main/testsuites/repos.robot

[SteveLasker]

👀
Thanks, folks. I'll get this incorporated next week.

[sajayantony]

Should we decide if this is the roadmap or not and close the PR?

[SteveLasker]

Yes, it's something I'd like to see incorporated.
I'm probably not the right person to write that code.
As it stands, this PR has helped others validate their registries support the OCI Artifacts requirements. So, it's useful even if just open. Better if it was merged as Josh suggested.

[sajayantony]

This was a good starting point for the discussions that lead OCI artifacts. Given that we now have - https://github.com/opencontainers/distribution-spec/tree/main/conformance and ORAS repo has all the E2E tests planned do we need this PR or can we close it @SteveLasker
ref : #639

[SteveLasker]

This was initially created to help docker enable oci artifacts. Now that they’re done, every other registry now enables OcI Artifacts, and there’s better codified solution, happy to close this one.