Answer

No. Hub will not propagate deletion of artifacts between repositories. 

Propagating deletions between repositories can be dangerous as it allows for unintended consequences between teams and with reporting. In addition, many tools do not support (or easily support) the ability to delete an artifact via Hub integration. 

It is recommended that admins disable the ability to delete artifacts (if supported by the repository) and instead add a special state of "deleted" to artifacts within the repository. This will allow for proper reporting of deleted items across the repositories and ensure that all artifacts in synchronization are properly updated.

Note that in the case of an artifact being deleted in one or more of the repositories being synchronized, Hub does provide some related features:

• Recreating a Deleted Artifact: If Hub is attempting to flow an update to a now-deleted artifact within a repository, you have the option of recreating its twin from the Activity screen. This will keep the newly recreated artifact in sync with the source artifact.
• Twinless Artifact Update: If an artifact is deleted or otherwise made ineligible for integration, you can configure a 'twinless artifact update' to notify that artifact's twin in the target repository, either via a comment or a field update.