There should be provision to provide cert as either a base64 encoded string or path to cert file

[bpradipt]

Today, AA and CDH accepts cert parameter which is a string. Example - https://github.com/confidential-containers/guest-components/blob/main/attestation-agent/attestation-agent/config.example.toml
This is bit fragile and can result in errors when copy/pasting the values.
A more robust mechanism is to either provide a base64 encoded cert or path to the cert file.

[Xynnn007]

I think the current cert is in base64 encoding?

Could you give an example for the base64 encoding format you've mentioned?

We can use a path to cert file, while for kata this would introduce more files (certs) included in initdata.