Pulp

+1 to the uniqueness constraint that's obviously missing.

For the name aspect, I suggest adding to the description that the name will be changed only if a better one can be agreed upon. I wouldn't want to hold up the rest of these improvements if we have trouble settling on a name.

One thing I'm not crazy about with regard to DeferredArtifact is that "defer" implies that retrieval has been delayed but will eventually happen. I think for most on-demand use cases, a lot of the content will never be retrieved, and that's an valued part of the feature.

It's often a good idea to focus on the nature of the data itself, not necessarily how or why it gets used. RemoteArtifact captures that it's a reference to a file outside of Pulp. ExternalArtifact might also work. ForeignArtifact says less about where the artifact is, but just focuses on the fact that it's not here. AvailableArtifact would heavily imply that the artifact is not locally stored, but that the record contains info on how to get it. ArtifactDownload emphasizes that this record is really about downloading, and the download info happens to be for an Artifact. OnDemandArtifact would match other language we use and I think is clear.

Any of that resonating well? Or sparking other ideas?

mhrivnak wrote:

+1 to the uniqueness constraint that's obviously missing.

For the name aspect, I suggest adding to the description that the name will be changed only if a better one can be agreed upon. I wouldn't want to hold up the rest of these improvements if we have trouble settling on a name.

Agreed. Let's deal with adding the unique constraint in a separate issue/pr.

The two names I am partial to are RemoteArtifact and ArtifactDownload. Since there's already been support raised for the former, I'm tempted to use it unless anyone opposes.