-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add feature pages for the REST API (resources and attestation) #76
Conversation
✅ Deploy Preview for frolicking-manatee-96c0c8 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
||
For example, you can run this command from your container. | ||
```bash | ||
curl http://127.0.0.1:8006/cdh/resource/default/key/1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can You add additional information about how to create such resource i.e.:
https://github.com/confidential-containers/trustee/blob/main/kbs/docs/resource_storage_backend.md
and information about corresponding config section:
[[plugins]]
name = "resource"
type = "LocalFs"
dir_path = "/opt/confidential-containers/kbs/repository"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Setting up resources is out of scope for individual features. The attestation section should describe how to do this rather than repeating it for every feature that relies on attestation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. One suggestion about 'sealed secrets' wording.
Description of how to get resources from containers Signed-off-by: Tobin Feldman-Fitzthum <[email protected]>
Describe how to enable and use the ASR to get attestation evidence. Also add a section about the evidence factory considerations. That is too complex a topic to get to the bottom of here, and we don't actually have a great solution to it until init-data support lands, but hopefully the note is useful. Signed-off-by: Tobin Feldman-Fitzthum <[email protected]>
1ca6673
to
0a07970
Compare
It's a bit tricky to address the evidence factory stuff, but hopefully the note there is useful.