registry: add reference

[craig-osterhout]

Description

Re-add registry reference from point in time of deletion at #18390, not upstream.

https://deploy-preview-22497--docsdocker.netlify.app/reference/api/registry/latest/
https://deploy-preview-22497--docsdocker.netlify.app/reference/api/registry/auth/

Related issues or tickets

ENGDOCS-2577

Reviews

• Technical review
• Editorial review
• Product review

[netlify]

✅ Deploy Preview for docsdocker ready!

Name	Link
🔨 Latest commit	e58a4e4
🔍 Latest deploy log	https://app.netlify.com/projects/docsdocker/deploys/682c9969428a7c0008427ce5
😎 Deploy Preview	https://deploy-preview-22497--docsdocker.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[sarahsanders-docker]

before I do a more thorough review, I left a comment about why we are not using an OpenAPI spec to generate the documentation here

[sarahsanders-docker]

I left a bunch of inline comments, but overall:

• For every endpoint, ideally we would have: Request syntax (covered this well) and a valid response example (we are missing these)
• Some of the steps feel like they are out of order. Maybe this is my misunderstanding of how to use the Registry API, but I left some comments about checking if layers/images exist coming before the rest of the steps.
• Lots of gerunds in headings make it hard to skim/find action oriented phrases, I would suggest changing the headings to remove gerunds so I can skim the content and look for actions I want to execute
• Lots of headings don't appear on the right TOC which makes it hard to skim and find what I am looking for. Ideally I would see the entire API in the TOC so I can jump to the endpoint I want

A good example format for endpoint patterns might be something like (this keeps it easy to skim and get all the info I need per endpoint):

Get image manifest

GET /v2//manifests/

Required headers:

• Accept: example
• Authorization: Bearer

Success response:

example of request response `200 OK` w/ Content-type

Possible errors:

• 401
• 404

Happy to help restructure this if you want me to overhaul the endpoint sections for you to commit changes @craig-osterhout

[craig-osterhout]

Did a complete overhaul of the pre-existing main content, migrated it to OpenAPI spec, and tested it.
The delete endpoint seems to not be enabled yet or has some nuance that I'm misunderstanding. Waiting to get details on that, but I think the editorial review can get started. Ideally, get this out as an mvp if it's all technically correct, and polish it in follow ups as I think this is now blocking an overdue critical project milestone.

[sarahsanders-docker]

@craig-osterhout if is blocking and technically correct, I can approve - editorial stuff will get addressed in the API reference project so we can tackle that in follow ups