Story #3636
closed
As a third party, I can use ids to interact with different endpoints
Description
Problem¶
In #3633, we exposed ids in responses. Now the problem is that the Katello/CLI/etc can't perform actions like publishing a repo version without the href. We need to figure out a way to let them use IDs.
Potential Solutions¶
1. Extend HyperlinkedRelatedField to accept ID in addition to href
2. Add another param for ID (e.g. repository_id) in addition to repository
3. ???
- Related to Story #3633: As a user, I am able to know the PK of each resource added
- Description updated (diff)
I think that Katello and other projects that integrate with Pulp should be able to store full relativate URIs for all resources that they need to be able to access at any time. The URIs would look like '/pulp/api/v3/repositories/<id>/'. The client would then need to be configured with Pulp's hostname, port, and prefix (for re-rooting the API). The client's can then use the hostname, port, prefix, and the full relative URI to properly form the URL for a resource that it already knows about.
@dkliban so basically Katello has to either:
1. Store id AND href
2. Know how to translate hrefs into ids for each resource
Either way, Katello has to deal with both ids and hrefs. I think Katello should just deal with ids or hrefs but not be forced to use both.
- Sprint deleted (
Sprint 36)
- Tracker changed from Issue to Story
- % Done set to 0
- Status changed from NEW to CLOSED - WONTFIX
We are no longer returning ids in our API and we decided to support hrefs only. Closing this out.
- Sprint/Milestone set to 3.0.0
Also available in: Atom
PDF
.