Project

Profile

Help

Story #5159

Updated by ttereshc over 5 years ago

h3. Motivation 

 
 There are situations when content in the storage needs to be repaired (while DB is fine and still contains all the data): 
  - file got corrupted for whatever reason 
  - file was removed from the storage by accident 
  - etc 

 Users need a way to solve those situations. 

 h3. Solution 

 
 Introduce an option @repair@ for the sync operation. It should be False by default. 
 When the @repair@ option is enabled, in the QueryExistingArtifacts stage make sure that the sha256 checksum of content in the storage is the same as stored in the DB.

Back