[Pulp-dev] [pulp 3] mutable Artifacts are too complicated
Dennis Kliban
dkliban at redhat.com
Thu Jul 20 16:09:36 UTC 2017
On Thu, Jul 20, 2017 at 11:21 AM, Jeff Ortel <jortel at redhat.com> wrote:
>
>
> On 07/20/2017 09:48 AM, Dennis Kliban wrote:
> >
> either of these scenarios is appealing to me. The REST API would be
> simplified if we made Artifacts
> > immutable. Either a plugin creates an Artifact once or an Artifact is
> created using the REST API. After that
> > it can only be retrieved or deleted.
> >
> > Any information, such as expected size and checksum should be stored in
> a separate table - together with the
> > URL of the remote artifact. We could call it RemoteArtifact.
>
> Just to clarify based on our discussions: The suggestion here is to
> broaden the scope of DownloadCatalog and
> rename to RemoteArtifact. Correct?
>
>
That is correct.
>
> _______________________________________________
> 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/20170720/88f861dd/attachment.htm>
More information about the Pulp-dev
mailing list