Skip to content

Document the rest_cherrypy /token and /app endpoints (#69726)#69727

Open
ggiesen wants to merge 1 commit into
saltstack:3006.xfrom
ggiesen:fix-69726-cherrypy-token-app-docs
Open

Document the rest_cherrypy /token and /app endpoints (#69726)#69727
ggiesen wants to merge 1 commit into
saltstack:3006.xfrom
ggiesen:fix-69726-cherrypy-token-app-docs

Conversation

@ggiesen

@ggiesen ggiesen commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

Adds the two missing sections to the rest_cherrypy REST URI Reference: POST /token (Token handler) and GET /app (App handler). Every other handler class on the page has an .. autoclass:: entry; these two were never included, so their endpoint docstrings (complete with request/response examples in Token's case) have never been rendered anywhere, and both endpoints are absent from the API reference and the HTTP routing table even though the running API routes them.

What issues does this PR fix or reference?

Fixes #69726

Previous Behavior

POST /token and GET /app were undocumented in the rendered docs.

New Behavior

Both endpoints appear in the REST URI Reference in the existing page style and are listed in the HTTP routing table.

Verified with the pinned docs toolchain (sphinx 7.0.1, sphinxcontrib-httpdomain 2.0.0): make html and make man build clean with -W -j auto --keep-going; both new sections render with properly transformed field lists and anchors (#post--token, #get--app); each route registers exactly once in the http domain, so this does not interact with the duplicate-route cleanup in #69725.

Merge requirements satisfied?

  • Changelog

Docs-only change; no runtime code paths affected.

Commits signed with GPG?

No

The REST URI Reference page has an autoclass section for every handler
class except Token (POST /token) and App (GET /app), so those two
docstrings were never rendered anywhere and both endpoints are missing
from the API reference and the HTTP routing table, despite being wired
up in the running API. Add the two sections following the existing page
style.

Both routes are unique, so this does not interact with the duplicate
route index cleanup in saltstack#69725; verified with the pinned docs toolchain
that html and man build clean under -W -j auto, both sections render
with transformed field lists and anchors, and each route registers
exactly once.

Fixes saltstack#69726
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test:full Run the full test suite

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants