Skip to content
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

storage corruption reporting #75

Open
wanderview opened this issue Sep 27, 2019 · 1 comment
Open

storage corruption reporting #75

wanderview opened this issue Sep 27, 2019 · 1 comment

Comments

@wanderview
Copy link
Member

Forked from #74.

I proposed a storage corruption proposal at TPAC:

https://github.com/wanderview/storage-corruption-reporting/blob/master/explainer.md

It seemed folks were generally agreeable to the use case of providing transparency. There are issues with using Reporting API, however. We discussed maybe exposing some reporting API surface of StorageManager instead.

Separately, though, @mikewest suggested we should try to improve Reporting API to support this reporting use case.

@annevk
Copy link
Member

annevk commented Sep 27, 2019

I mentioned it in the other issue, but the use case that was compelling to me was not so much reporting, but being able to tell your bucket is corrupted and having control over how that's handled.

Reporting might be useful too, but it seems strictly less interesting. However, if when the user navigates to an origin and we detect the bucket for that origin is corrupted, what are the issues with using reporting infrastructure to report this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants