Introduction
When using federated repositories, there are some artifact metadata that will be different after the artifact is synchronized. Such as created time, lastModified time and deployedBy of artifact are different due to different deployer and deployment complete time.
How to synchronize them between source repository and target repository?
Resolution
From Artifactory 7.90.1 release, there is a system property “artifactory.federated.mirror.events.upload.info.propagate.enabled” and the default value is false.
Set artifactory.federated.mirror.events.upload.info.propagate.enabled=true in the artifactory.system.properties located under $JFROG_HOME/artifactory/var/etc/artifactory in both source and target JPDs.
Then save and restart both Artifactories to make the setting effective.
After that, the attribute of created time, lastModified time and deployedBy will be synchronized to the target repo.
Important Note
Please note that adding this system property will not retroactively change the metadata for artifacts that have already been synchronized prior to enabling the property.
Workaround for Existing Artifacts
If you need to propagate the original metadata for artifacts that were synchronized before the property was enabled, there is a workaround. If your federation is utilizing a Circle of Trust (COT), you can force a fresh sync of the metadata by recreating the target member:
- Create a new federated repository on the Target JPD.
- Disconnect/remove the old repository member in the Source JPD.
- Add the newly created target repository as a member to the Source JPD.
- Initiate a FullSync from the Source using the following REST API:
curl -u 'admin:password' -XPOST 'https://<RT_URL_SOURCE>/artifactory/api/federation/forceFullSync/<FEDERATED_REPO_NAME>
Before: (Notice the local upload time and generic 'anonymous (federated)' deployer)
After: (Notice the original deployer ID and original timestamps are preserved)
