Polish the MVC end-to-end Attestation workflow

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

We are very close to working end-to-end MVC Attestation workflow 🎉 🎉

I my testing today I was able to:

  1. Build a ruby gem in CI and upload it as a job artifact.
  2. Generate the provenance and an attestation for the artifact.
  3. Look up the attestation record by the digest of the artifact.
  4. I was not able to download the attestations for verification from the API.
  5. I was able to download attestation via the download route, but I had to look up the iid in the DB.
  6. Verify the attestation using cosign.

I think the main thing missing at this point is a way to get to the attestation bundle from the API. To solve for this, a couple of options come to mind:

  1. We could add the download path as an attribute in the API response.
  2. We could include the full attestation bundle in the API response. Similar to other platforms.
  3. We should also add the iid to the API response for completeness, but I don't think this should be our only reference to the attestation bundle file.

@sroque-worcel @ahuntsman What do you think about these options? Are there other ways we could solve for this?

/cc @ken.mcdonald

Notes

Edited by 🤖 GitLab Bot 🤖