[Pulp-dev] Pulp api seemingly incompatible with generated bindings

[Tom McKay]

If I'm deploying pulp in openshift, my "hostname" can vary greatly since
comms go through a router. Would you want to save
docker-registry.192.168.100.1.nip.io in the database?


apiVersion: v1
kind: Route
metadata:
  name: registry-access
spec:
  host: docker-registry.`minishift ip`.nip.io
  to:
    kind: Service
    name: docker-registry
    weight: 100
  port:
    targetPort: 5000-tcp
  tls:
    termination: edge
    insecureEdgeTerminationPolicy: Allow
status:


On Mon, Apr 30, 2018 at 10:53 AM, David Davis <daviddavis at redhat.com> wrote:

> > If one changes an object's attributes (e.g. UUID), its href doesn't
> change.
>
> UUIDs don’t change. In fact, I think UUIDs are truly immutable compared to
> hrefs which might change if hostname/port/scheme/deployment path/etc
> change.
>
>
> David
>
> On Mon, Apr 30, 2018 at 10:46 AM, Jeremy Audet <jaudet at redhat.com> wrote:
>
>> > +1. Exposing UUIDs is definitely preferable to using hrefs as ids.
>>  "The app just looks at the relative path"  -> what if pulp wants the
>> flexibility to change repositories end point (highly improbable but you
>> never know).
>>
>> Is it better, though? URIs were chosen specifically with immutability in
>> mind. "Cool URIs don't change." This is reflected in the application's
>> behaviour. If one changes an object's attributes (e.g. UUID), its href
>> doesn't change.
>>
>> And in what case are hostname and port changing? If that's a common
>> deployment issue, I would contend that the deployment at hand is screwed up.
>>
>
>
> _______________________________________________
> 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/20180430/35c41f94/attachment.htm>