Pulp

Since artifacts are shared, there will be cases where a newly downloaded Artifact is referenced by more than one ContentArtifact. The component that creates the Artifact could be an importer, upload or task related to deferred downloading. It will be doing so with knowledge of a specific remote artifact (aka DeferredArtifact, RemoteArtifact, ..) but won't know about other references. But the other references can be found and updated by searching remote artifact by digest. Then, update the associated ContentArtifacts.

The how/where this update gets run is still unaccounted for. This mainly (maybe only) affects deferred downloading users.

A few approaches might be:

1. The deferred downloading task could update other references after creating an artifact.
2. Add a save signal handler to the artifact. The handler would perform the update described above.
3. We could add a created field on Attribute. Then have a periodic task search for artifacts created since the task last ran and ensure all references are updated.
4. Other?