Configs pushed to OCI registries are not valid artifacts #1508
Description
Describe the bug
When pushing a YAML config to an OCI registry, the generated image is NOT a spec compliant artifact. It saves as if it is a runnable container image, which confuses tooling. This page specifies artifact guidance - the short version is we either need to set an artifactType on the root manifest, or set a non-image mediaType on the config. I tried doing a PR to set this using crane, but it seems that tooling is not working as expected, nor does it support artifactTypes. I'd suggest a larger refactor to use a different library for building/sending images, such as this one.
A clear and concise description of what the bug is.
Version affected
Please include the version of the software that you are using.
(paste the output of the version command)
How To Reproduce
- Run
cagent push ./golang_developer.yaml <my_namespace>/<test_repo> - View image on oci.dag.dev
- See image is not valid artifact
Detailed steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expectation
A clear and concise description of what you expected to see/happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Especially useful if the problem is visual (rendering issues etc.) or you're not totally sure how to explain the problem and need to show it to us
OS and Terminal type
Please include what OS and terminal you are using
Additional context
Any other info you consider useful can be included here