confidential-containers / trustee

Attestation and Secret Delivery Components
Apache License 2.0
51 stars 77 forks source link

CI: set expected tee in policy within the kbs e2e test #401

Closed mkulke closed 1 month ago

mkulke commented 1 month ago

The e2e tests used to remove the tee != sample restriction from the policy prior to testing. Since we want to avoid using the sample attester accidentally, we can set the expected TEE in the policy.

The TEE e2e tests would fail here, because the interface of the workflow has been changed (introduced mandatory tee input) and it will be executed with the workflow from the main branch.

I ran the workflow is a discrete branch to test here (using tee: aztdxvtpm)