Prior to the migration, when Artifactory used the “eventual” provider, it had 2 directories through which events were sent to the Cloud provider, $EVENTUAL/_add/ and $EVENTUAL/_delete/.
Once “eventual-cluster” is used, Artifactory doesn’t check the above directories, but rather the $EVENTUAL/_queue/ directory. In case there are leftovers in either the “_add” or the “_delete”, we will need to move them to the “_queue” directory in order to process these events.
The main difficulty here is that the expected file name format is different.
To overcome this, here is a script you can run that will move/copy the files to the target directory in the expected format.
After running the script, Artifactory will automatically pick up the events from the “_queue” folder. No additional restart is required.
eventual2cluster
Important! Prior to running the script make sure to review the README notes.
Once “eventual-cluster” is used, Artifactory doesn’t check the above directories, but rather the $EVENTUAL/_queue/ directory. In case there are leftovers in either the “_add” or the “_delete”, we will need to move them to the “_queue” directory in order to process these events.
The main difficulty here is that the expected file name format is different.
To overcome this, here is a script you can run that will move/copy the files to the target directory in the expected format.
After running the script, Artifactory will automatically pick up the events from the “_queue” folder. No additional restart is required.
eventual2cluster
Important! Prior to running the script make sure to review the README notes.