On 07/20/2017 09:48 AM, Dennis Kliban wrote: > > Neither 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?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
