Ruby bindings send PRNs as hrefs to Pulp API

[ianballou]

Version

      "versions": {
        "deb": "3.7.0",
        "rpm": "3.32.0",
        "core": "3.85.1",
        "file": "3.85.1",
        "ostree": "2.5.0",
        "python": "3.19.0",
        "ansible": "0.28.0",
        "certguard": "3.85.1",
        "container": "2.26.1"
      }

Describe the bug
I noticed a couple API endpoints that reportedly should accept both hrefs and PRNs 404 when a PRN is sent:

> <UploadResponse> update(content_range, upload_href, file, opts)

Upload a file chunk

Upload a chunk for an upload.

> <TaskResponse> read(task_href, opts)

Inspect a task

Error I captured:
 777f8c1a | ActionController::RoutingError (No route matches [GET] "/prn:core.task:01997816-58f6-71e2-9bd9-e49554e2404a"):

To Reproduce
Use the Ruby bindings to read a Task is the most straight-forward one.

Note, there may be other endpoints too. I've only identified 2. Perhaps the PRN/href mixin isn't working specifically with the Ruby bindings?

Expected behavior
PRN should be used where an HREF is expected.

Additional context
Katello is removing all use of HREFs to prepare for Pulp 4.

[ggainey]

The upload() call is definitely a bug - you can use HREFs or PRNs as fields to a route, and the Ruby binding failing there is something we need to fix.

The task-GET, however, is not a bug. You can't retrieve an instance with a "naked" PRN - you must have the routing information. We'll keep this issue, but only for the update() problem.

[ianballou]

The task-GET, however, is not a bug. You can't retrieve an instance with a "naked" PRN - you must have the routing information. We'll keep this issue, but only for the update() problem.

Ah, yes this makes sense now.

(As discussed elsewhere, Katello realizes now that Pulp won't be completely getting rid of hrefs.)