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 <[email protected]> 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 <[email protected]> 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
> [email protected]
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
_______________________________________________
Pulp-dev mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-dev
