Project

General

Profile

Bug #27673

Repository Set API lists input paramter "id" as number, which potentially excludes Candlepin content id values

Added by Evgeni Golov over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
API
Target version:
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Api::V2::RepositorySetsController expects :id to be :number for /repository_sets/:id, /repository_sets/:id/available_repositories etc.

However, since this input parameter might also refer to a Candlepin content id as well as Katello db id, Candlepin content ids that are not numbers cannot be used.


Related issues

Related to Foreman - Tracker #27680: API bugs that need workarounds in foreman-ansible-modulesNew

History

#1 Updated by Samir Jha over 2 years ago

  • Triaged changed from No to Yes
  • Difficulty set to trivial
  • Target version set to Katello 3.14.0

#2 Updated by Evgeni Golov over 2 years ago

  • Related to Tracker #27680: API bugs that need workarounds in foreman-ansible-modules added

#3 Updated by James Jeffers over 2 years ago

  • Assignee set to James Jeffers

#4 Updated by James Jeffers over 2 years ago

The id is actually the Candlepin content id, which may be a non-integer.

#5 Updated by James Jeffers over 2 years ago

  • Target version changed from Katello 3.14.0 to Katello Recycle Bin
  • Status changed from New to Rejected

#6 Updated by James Jeffers over 2 years ago

  • Target version changed from Katello Recycle Bin to Katello Backlog
  • Assignee deleted (James Jeffers)
  • Status changed from Rejected to New
  • Subject changed from Repository Set API returns ID as String, but expects Integer to Repository Set API lists input paramter "id" as number, which potentially excludes Candlepin content id values

#7 Updated by James Jeffers over 2 years ago

  • Description updated (diff)

#8 Updated by James Jeffers over 2 years ago

  • Difficulty changed from trivial to medium

Discussed this topic with Katello team members. The change itself would be trivial, but the implications of doing so are not understood well enough to proceed. For example, what other clients rely on the current input format? It's not known at this point, so more investigation is required.

Also available in: Atom PDF