Closed Xynnn007 closed 2 months ago
Rebased and ready for review. cc also @imlk0
Rebased and ready for review. cc also @imlk0
Thanks @Xynnn007. That solves my problem.
In some scenarios, callers want to get the name of current platform.
I think it would be good to clarify in the commit message what are the scenarios and who are the callers.
I think it would be good to clarify in the commit message what are the scenarios and who are the callers.
Yes. Added the details. AA can run outside CoCo scenarios. For example, AA would run on an IaaS platform, and a user of such IaaS platform could get the tee type. Another example is some PaaS services on top of such IaaS platform, they also want to know the platform name.
AA would run on an IaaS platform, and a user of such IaaS platform could get the tee type.
I was suspecting it might be something like this. It makes me think if it overlaps with what node-feature-discovery already gives.
AA would run on an IaaS platform, and a user of such IaaS platform could get the tee type.
I was suspecting it might be something like this. It makes me think if it overlaps with what node-feature-discovery already gives.
Yes. As a confidential runtime component, AA should have such ability itself.
This new API is used for a caller to get current platform name.
---New things added
In some scenarios, callers want to get the name of current platform. Thus we need this basic semantics for AA.