[Pulp-dev] Object IDs in Pulp 3

Dennis Kliban dkliban at redhat.com
Wed Jan 3 18:05:19 UTC 2018

We should probably expose the ID field in the REST API.

CLI should convert a resource type and UUID into a URL. CLI users should be
able to specify a UUID when referencing a resource.

The REST API only cares about the relative path after the hostname[0].
Katello can store either the full URL or just the relative path. We should
provide some documentation for REST API users to suggest that resources
should be compared without the protocol, hostname, or port.

[0] https://pulp.plan.io/issues/3024

On Wed, Jan 3, 2018 at 12:32 PM, David Davis <daviddavis at redhat.com> wrote:

> I’ve been working on and discussing an issue with @asmacdo about filtering
> by id [0] and it’s brought up some questions about how repos, importers,
> etc should be identified in Pulp 3. I think currently we uniquely identify
> object’s by their href field since names are mutable. The main questions
> are: how should things like Katello store ids for objects like repos?
> Moreover, what identifier would a user use to look up an object in the
> CLI—would they pass the object’s href?
> I imagine right now that Katello would store an object’s href since we
> don’t expose object’s ids. But what if the hostname changes or Pulp
> switches from http to https. Then the object's identifier would change.
> Similarly, as a CLI user, what could I use to uniquely identify say a
> repo? Supplying the object’s href seems a bit strange I guess since you
> wouldn’t expect hyperlinks in a command line interface. Would CLI users
> deal with names? Those can change though which would be bad for setting up
> things like cron jobs using the CLI.
> Any thoughts?
> [0] https://pulp.plan.io/issues/3240
> David
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180103/85c7226b/attachment.htm>

More information about the Pulp-dev mailing list