Skip to content

Fixes #40037 - Fix ptables/revision routes - #11380

Open
ofedoren wants to merge 3 commits into
theforeman:developfrom
ofedoren:bug-40037-fix-ptable-routes
Open

ofedoren wants to merge 3 commits into
theforeman:developfrom
ofedoren:bug-40037-fix-ptable-routes

Conversation

@ofedoren

@ofedoren ofedoren commented Nov 11, 2026 •

Copy link
Copy Markdown
Member

More info in the https://projects.theforeman.org/issues/40037. Found as part of #11377.

lzap
lzap previously approved these changes Nov 11, 2026

@lzap lzap left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Untested

@ofedoren

Copy link
Copy Markdown
Member Author

I've changed the PR a bit:

  • The first commit is just the straightforward fix, the simplest way (the smallest change)
  • The second commit uses a bit stricter approach trying to be as safe as possible (a bit safer change compared to the first one)
  • The third commit tries to get the routes definition in order (a bigger change)

I can leave any combo of the commits, although I'd prefer to include all of them and squash.

Move the revision collection route into the earlier constrained ptable declaration. Keep the complete resource declaration unconstrained so child IDs retain their format suffix parsing while dotted ptable IDs remain supported.

Cover locations, organizations and operating systems with and without JSON suffixes under both API URL forms.
Use one resource declaration and define standard member routes explicitly so dotted ptable IDs remain supported without constraining nested resource IDs. Declare collection routes first to preserve revision routing.

Cover CRUD and custom routes, nested operating system actions and URL helpers for both API URL forms.
@ofedoren
ofedoren force-pushed the bug-40037-fix-ptable-routes branch from 3ef19b5 to c06018e Compare November 12, 2026 19:58

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants