Feature #17030
CP 2.0: Phase 2: Investigate swagger-based api gem
| Status: | New | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Candlepin | ||
| Target version: | Katello Backlog | ||
| Difficulty: | Team Backlog: | Brad | |
| Triaged: | Yes | Fixed in Releases: | |
| Bugzilla link: | Found in Releases: | ||
| Pull request: | |||
Description
Candlepin 2.0 supports a swagger-based API. This enables users (such as katello) to create ruby bindings using swagger tooling. This could effectively remove the need for the legacy ruby bindings in katello's candlepin.rb.
In addition, there is a desire to evolve the current katello-candlepin functionality to support a gem similar to what was done in the past for the katello-pulp functionality via the runcible gem. The thought would be to refactor generic logic (that is not specific to katello) out of katello. (This may include code under app/models/katello/glue/candlepin.)
With this issue, should investigate what it would mean to support:
- generating and using swagger api bindings
- refactoring generic candlepin functionality to a separate gem (similar to runcible)
As part of completion, a high-level design/proposal should be submitted as an RFC [1]. Once review is completed, further task breakdown can be performed.
Related issues
History
#1
Updated by Brad Buckingham over 1 year ago
- Blocks Tracker #17020: Tracker: Candlepin 2.0 Integration added
#2
Updated by Chris Roberts over 1 year ago
- Assignee deleted (
Chris Roberts)
#3
Updated by Brad Buckingham over 1 year ago
- Target version changed from 133 to 140
#4
Updated by Brad Buckingham over 1 year ago
- Target version changed from 140 to 147
#5
Updated by Brad Buckingham over 1 year ago
- Target version changed from 147 to 151
#6
Updated by Brad Buckingham over 1 year ago
- Target version changed from 151 to 157
#7
Updated by Brad Buckingham over 1 year ago
- Target version changed from 157 to 160