Submission Artifacts Mapping

[sharathkumaranbu]

• Create submission-artifact table in dynamodb to maintain the artifact-submission mapping

• Use new table to search the artifacts instead directly querying s3 bucket

• Place the artifact in new folder structure, refer following section
  

[callmekatootie]

@rootelement The changes are currently in branch Issue_170.

Since we need to make this backward compatible, can you let me know if the following behaviour would be the right way:

• for CREATE, we will first check if there are any artifacts for the submission through the old approach.
  • If yes, then we will continue to create the artifact through the old approach
  • If no, then we will create the artifact through the new approach
• for LIST, we will first check for artifacts through the new approach. If no artifact is returned, then we will check for artifacts through the old approach
• for DOWNLOAD, we will first check for existence of the artifact through the new approach. If none is found, we will check for existence of the artifact through old approach and then download the artifact based on the location identified
• for DELETE, we will first check for existence of the artifact through the new approach. If none is found, we will check for existence of the artifact through old approach and delete it when found.