[Pulp-dev] Name uniqueness problem in Pulp 3 REST API

[David Davis]

Agreed.

David


On Tue, Jul 21, 2020 at 8:42 AM Grant Gainey <ggainey at redhat.com> wrote:

> On Tue, Jul 21, 2020 at 8:14 AM Dennis Kliban <dkliban at redhat.com> wrote:
>
>> Does anyone else have an opinion? If not, I am going to start by writing
>> a task to remove this name uniqueness constraint for repositories.
>>
>
> Import/export relies on non-pulp_id-uniqueness to identify Things. I was
> assuming we were talking about adding pulp_type to the Repository
> uniqueness-constraint, so that a given name/type would be unique (which
> would require a single change to RepositoryResource
> <https://github.com/pulp/pulpcore/blob/master/pulpcore/app/modelresource.py#L35>
> )
>
> If we're talking about just removing the uniqueness-constraint altogether,
> then life gets a lot harder.
>
> G
> --
> Grant Gainey
> Principal Software Engineer, Red Hat System Management Engineering
> _______________________________________________
> 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/20200721/167468a8/attachment.htm>