JFrog Distribution includes a service that periodically collects metadata about Release Bundle versions that have been deleted locally from a distribution target (typically an Edge node) and sends the information to the source Artifactory. These local deletions are then added by Artifactory as events in the timeline of the relevant Release Bundle version.
This service was created because Edge nodes cannot initiate communication on their own with Artifactory instances.
Note
The target scraping service requires Distribution 2.24.0 or higher and Artifactory 7.84.3 or higher. Any Release Bundles that were distributed before both supported versions were installed cannot be scraped and reported by this service.
Distribution Configuration
The scraping service is configured in the Distribution config YAML, as shown below. There is generally no need to change the default settings.
task:
deleted-at-target-scraping:
batch-size: 200 # number of returned records per request
interval-seconds: 900 # interval between successive runs of the delete at target scraping jobArtifactory Configuration
The Artifactory side of the scraping service is configured in the system YAML, as shown below.
artifactory:
target:
bundle:
actions:
cron: "0 0 2 ? * * *"
deleteAfterHours: 720
Parameter | Description |
|---|---|
DEFAULT_CRON_PATTERN | The cron pattern that defines when the source Artifactory informs the distribution target to delete the metadata records of deletion events that have been handled by the scraping service. The default is |
DEFAULT_DELETE_ACTIONS_AFTER_HOURS | Determines when to delete leftover metadata that was not deleted by the DEFAULT_CRON_PATTERN. The default is |