Codecov Report

Attention: Patch coverage is 77.55102% with 11 lines in your changes missing coverage. Please review.

Project coverage is 65.43%. Comparing base (5a22ac2) to head (00f5a98).
Report is 2 commits behind head on main.

@@           Coverage Diff           @@
##             main     #314   +/-   ##
=======================================
  Coverage   65.42%   65.43%           
=======================================
  Files          53       53           
  Lines        4318     4319    +1     
=======================================
+ Hits         2825     2826    +1     
  Misses       1218     1218           
  Partials      275      275           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

@danko-miladinovic please review this one.

Is maybe Attestation Report, or Attestation Measurement better naming for this? This is why I asked for IETF RATS terminology, to better understand if this is the best term, as is not self-explanatory to e as Backend Info was.

The name is fine. The attestation policy json file (previously backend info) is used for verification and validation of attestation request. It contains information that are used by the go-sev-guest library to verify/validate the report. In RATS terminology the attestation policy would be equivalent to Appraisal Policy for Evidence or Appraisal Policy. The Attestation Policy name is fine because besides the values that it holds (measurement, minimum TCB, and so on) it also holds the values needed for the CLI to fetch certificates from the AMD KDS.